Devtools' own CSS triggers Browser Console errors for invalid variables, like "Property contained reference to invalid variable. Error in parsing value for ‘color’. Falling back to ‘inherit’. styles.css:368:6723"
Categories
(DevTools :: Console, defect, P3)
Tracking
(Not tracked)
People
(Reporter: dholbert, Unassigned)
References
Details
Attachments
(1 file)
279.93 KB,
application/gzip
|
Details |
Reporter | ||
Comment 1•8 years ago
|
||
Reporter | ||
Comment 2•8 years ago
|
||
Reporter | ||
Comment 3•8 years ago
|
||
Reporter | ||
Comment 5•8 years ago
|
||
Reporter | ||
Comment 6•8 years ago
|
||
Comment 7•8 years ago
|
||
Comment 8•8 years ago
|
||
Updated•6 years ago
|
Reporter | ||
Comment 10•6 years ago
•
|
||
Sure! BTW, with current Firefox Nightly, this step from comment 0...
- Click the dropdown arrow next to "CSS" and click "Warnings" (so that CSS Warnings are enabled).
...should now read:
- Click the funnel icon to the left of "filter output", and click "CSS" to make sure that's active.
And I can't proceed past that step, I think, because it looks like that option is just broken -- it triggers some JS errors when I activate it, which I filed as bug 1523020, and which gives me a low level of confidence that CSS errors are actually going to be logged successfully.
Updated•6 years ago
|
Comment 11•6 years ago
|
||
I see, thanks for the update.
Reporter | ||
Comment 12•6 years ago
|
||
(If I ignore the fact that those JS errors are logged -- i.e. if I ignore bug 1523020 -- then this seems superficially WORKSFORME in that I never see any CSS parsing errors appear in the Browser Console. Instead, I only see JS errors, for css-related devtools stuff. At first I thought that meant this was fixed, but now I'm suspicious that there could easily still be CSS parsing errors lurking and we just don't get far enough to be able to report them anymore, due to bug 1523020.)
Updated•2 years ago
|
Description
•