Open
Bug 1261237
Opened 9 years ago
Updated 2 years ago
browser_parsable_css.js should parse things as chrome
Categories
(Firefox :: General, defect)
Tracking
()
NEW
People
(Reporter: MatsPalmgren_bugz, Unassigned)
References
Details
Follow-up from bug 1025267:
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #14)
> (In reply to Boris Zbarsky [:bz] from comment #13)
> > We may want a test that checks that these pseudos are in fact parseable in a
> > chrome sheet; followup is ok for that test.
>
> This may already be covered by
> http://hg.mozilla.org/mozilla-central/file/60b269fed8cf/browser/base/content/
> test/general/browser_parsable_css.js since the styles exist in a chrome
> stylesheet and that test confirms that none of our front-end CSS contains
> parsing errors.
(In reply to :Gijs Kruitbosch from comment #16)
> (In reply to Boris Zbarsky [:bz] from comment #15)
> > Um... that test should really parse things as chrome, which is how they
> > would actually get parsed. :( Ah, well.
Reporter | ||
Comment 1•9 years ago
|
||
Bug 1261239 is about bz's first suggestion above - to have a dedicated test that tests
all supported pseudos (independent of actual use in Firefox style sheets, which
I assume is what browser_parsable_css.js is about).
Comment 2•9 years ago
|
||
(In reply to Mats Palmgren (:mats) from comment #1)
> Bug 1261239 is about bz's first suggestion above - to have a dedicated test
> that tests
> all supported pseudos (independent of actual use in Firefox style sheets,
> which
> I assume is what browser_parsable_css.js is about).
Yes. As I noted in bug 1025267 comment 16, I think it should already be doing that. It would be worth checking...
Blocks: 1207443
Updated•6 years ago
|
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•