On Mon, Nov 24, 2008 at 6:49 PM, Boris Zbarsky <[EMAIL PROTECTED]> wrote: > Ok. Bugs filed? This would need new APIs into the selector-matching > engine, and it's not obvious what the right APIs would look like. For > example, what should happen with rules like "div:hover > p" when looking at > paragraphs?
I think you would want to catch those ones too. When I look with the dom inspector and I want to see all css rules involved with an element, I also would like to see the relevant css rules that have dynamic pseudo-classes in them. Regards, Martijn >> Is there anything like an 'onHover'? onContentStateChange? Firebug could >> at least reflect the hover change in its UI if it got an event. > > onMouseOver, no? > > There is no generic notification for content state changes (or even just > event state changes; content state includes things like :default that are > not managed by the ESM). > > -Boris > _______________________________________________ > dev-tech-layout mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-tech-layout > -- Martijn Wargers - Help Mozilla! http://weblogs.mozillazine.org/qa/ http://wiki.mozilla.org/Mozilla_QA_Community irc://irc.mozilla.org/qa - /nick mw22 _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
