"the definition is quite good, but it's not clear what you can expect" KHTML returns some "computed" selector text (or "mis-computed, as it appears). It's a bug. Mozilla may also have a bug, it appears. It would be kind of you to file a bug on https://bugzilla.mozilla.org/ and provide a testcase demonstrating the behavior you described, Lots of improvements could be made regarding the Style module. For example, getting selectorText as a List of Selector objects would be very useful. Selector objects could then have a specificity property. On 6/7/06, Daniel Glazman <daniel.glazman@disruptive-innovations.com> wrote: > > Anne van Kesteren wrote: > > > It would be nice if the next revision, or perhaps some agreed upon > > algorithm between different vendors is created, so that interoperability > > becomes better and we don't have to reverse engineer each other ;-) > > Anne, we all know the CSS OM needs a __complete__ revamping. > > </Daniel> > > -- http://dhtmlkitchen.com/ -- http://dhtmlkitchen.com/Received on Wednesday, 7 June 2006 19:33:26 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:45 GMT