Closed
Bug 591349
Opened 15 years ago
Closed 15 years ago
csslogic discovers DOM Rules with no selectorText
Categories
(DevTools :: General, defect)
DevTools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jwalker, Unassigned)
References
Details
(Whiteboard: [kd4b6])
It's not clear that this is reproducible yet, however I'd like to leave a bug so we don't forget.
See csslogic.js around line 456
Reporter | ||
Comment 1•15 years ago
|
||
It does look reproducible.
See http://getfirebug.com/firstrun#Firebug%201.6.0b1
![]() |
||
Comment 2•15 years ago
|
||
That's interesting. Will test soon.
My initial thought was that domRules without .selectorText can only come from elements that have .style. Still, we have to check the CSS specs and see on that page you linked what happens.
![]() |
||
Updated•15 years ago
|
Whiteboard: [kd4b6]
![]() |
||
Comment 3•15 years ago
|
||
Just checked the spec:
http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSRule
There are CSSRules that have no .selectorText. I think we want to skip those that do not have .selectorText. We should only care about @imports, and possibly @media rules.
Reporter | ||
Comment 4•15 years ago
|
||
I have added an escape for this already, but we should possibly check the .type rather than .selectorText. Arguments both ways, but possibly we can just leave the code as it is now with the removal of a comment.
Reporter | ||
Comment 5•15 years ago
|
||
This is fixed (with a comment) in the main patch now.
Mihai's current performance patch removes the comment, which is the correct thing to do.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•