Erroneous style rule being reported in document.stylesheets, but not being applied

RESOLVED WORKSFORME

Status

()

Core
DOM: CSS Object Model
--
minor
RESOLVED WORKSFORME
7 years ago
7 years ago

People

(Reporter: Cory Mawhorter, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Firefox/3.6.15 ( .NET CLR 3.5.30729; .NET4.0E)

Iterating over the rules in document.stylesheets of the acid2 test reports line 96 as an active rule for .parser, however it is not applied to the element on the page (thus the acid2 test at webstandards.org looks fine).  

Line 96: "\.parser { padding: 2em; }"

With firebug installed, you can see this illustrated.  Inspect .parser and you will not see anything related to line 96 in CSS for the element, but then click on the CSS tab and line 96 will appear.  

This appears to have been fixed in ff4 minefield as the line is still reported, but it is reported accurately as "\.parser { padding: 2em; }" instead of ".parser { padding: 2em; }"

Reproducible: Always
Sounds like this is fixed, then...  This isn't a security issue, so won't be backported to the security-fix branches.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
Either way, though, it's not an *erroneous* style rule.  It's a style rule with a tag selector for an element with tag name ".parser".
(Reporter)

Comment 3

7 years ago
Didn't know 3.6 is security only.  Sorry about that.  

Just to defend my original report =] -- The rule is reported to Javascript as simply ".parser", which is incorrect.  It should either report to javascript as "\.parser", or apply the style to elements with classname ".parser".  It does neither.  This isn't a huge problem, as anyone who makes a classname "\.parser" is wrong.  But still, it is/was an problem.
You need to log in before you can comment on or make changes to this bug.