Can't expand CSS messages
Categories
(DevTools :: Console, defect)
Tracking
(firefox-esr68 unaffected, firefox70 unaffected, firefox71 unaffected, firefox72 fixed)
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox70 | --- | unaffected |
firefox71 | --- | unaffected |
firefox72 | --- | fixed |
People
(Reporter: mbalfanz, Assigned: nchevobbe)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
In the latest Nightly [72.0a1 (2019-11-04) (64-bit)], the expandable arrows don't work anymore and throw an error in the browser toolbox (see attachement)
STR:
- visit for example https://www.nytimes.com/ and open the console
- look for any CSS warning and try to expand the message
ER: the message should expand
AR: nothing happens
Reporter | ||
Comment 1•5 years ago
|
||
Please note that the second warning ("options is undefined") appears when trying to toggle the same arrow a second time.
Reporter | ||
Comment 2•5 years ago
•
|
||
Assignee | ||
Comment 3•5 years ago
|
||
The fix should be easy (default the option
variable to empty object).
It wasn't caught by a test because we only have a mocha test for CSS warnings, so we never assert that we are retrieving the impacted elements; i'll add a mochitest for that.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
The issue was in commands.js evaluateJSAsync function where
we were trying to use an undefined parameter.
The regression wasn't spooted earlier because we only have
mocha test for CSS warning, and they don't assert this
codepath.
A mochitest is added on this patch to ensure CSS Warnings
can be expanded, that they display the impacted elements
as expected, and that clicking on the icon selects the
expected element in the inspector.
Pushed by nchevobbe@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9fd1d61b2ffa Fix issue when expanding CSS warnings. r=rcaliman.
Updated•5 years ago
|
Comment 6•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Updated•2 years ago
|
Description
•