Closed Bug 1593654 Opened 5 years ago Closed 5 years ago

Can't expand CSS messages

Categories

(DevTools :: Console, defect)

defect
Not set
normal

Tracking

(firefox-esr68 unaffected, firefox70 unaffected, firefox71 unaffected, firefox72 fixed)

RESOLVED FIXED
Firefox 72
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:

  1. visit for example https://www.nytimes.com/ and open the console
  2. look for any CSS warning and try to expand the message

ER: the message should expand
AR: nothing happens

Please note that the second warning ("options is undefined") appears when trying to toggle the same arrow a second time.

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: nobody → nchevobbe
Status: NEW → ASSIGNED
Regressed by: 1580165
Summary: Expandable arrows don't work → Can't expand CSS messages

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.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 72
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: