Issue metadata
Sign in to add a comment
|
Regression : Styles in 'Element' section appears blank after running audit in devtools.
Reported by
rp...@etouch.net,
Jan 24 2018
|
||||||||||||||||||||||
Issue description
Version: 66.0.3330.0 (Official Build) Revision44fe59c8dd90d446da8eceda0cb28a5117311be1-refs/heads/master@{#531403}(32/64-bit)
OS: Mac OS X(10.12.6,10.13.1)
What steps will reproduce the problem?
1. Launch chrome, navigate to NTP and open devtools
2. Now go to 'Audits' section and run audit.
3. Now go to 'Element' section and observe
Actual: Styles in 'Element' section appears blank after running audit
Expected: Styles in 'Element' section should not appear blank after running audit
This is regression issue, broken in ‘M 66’ and will soon update other info
Good build: 66.0.3328.0
Bad build: 66.0.3329.0
,
Jan 24 2018
Adding release blocker label for this issue.Please reduce priority or remove if not the case. Thank You!
,
Jan 24 2018
My change only affects android. https://chromium-review.googlesource.com/875141 actually changes devtools. Assigning to dgozman@
,
Jan 26 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/bba4afa414f8069aec8d5cff829b4a278766a76d commit bba4afa414f8069aec8d5cff829b4a278766a76d Author: Dmitry Gozman <dgozman@chromium.org> Date: Fri Jan 26 23:16:28 2018 [DevTools] Set rootDOMNode on ElementsTreeOutline when loading ElementsPanel When showing ElementsPanel, all the tree outlines are not wired to DOMModels yet, and therefore did not updated root node with a document. We used to manually do that from ElementsPanel, but removed it recently. Bug: 805353 Change-Id: I2b15a2368de92bcda090b95f22e912e553badd9b Reviewed-on: https://chromium-review.googlesource.com/887648 Reviewed-by: Pavel Feldman <pfeldman@chromium.org> Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#532085} [modify] https://crrev.com/bba4afa414f8069aec8d5cff829b4a278766a76d/third_party/WebKit/Source/devtools/front_end/elements/ElementsPanel.js
,
Jan 26 2018
,
Jan 29 2018
Rechecked the above issue on Mac OS X(10.12.6,10.13.1) with latest canary chrome version : 66.0.3334.0 and the issue is still reproducible.Kindly refer attached screen cast for reference.
,
Jan 29 2018
Hmm... I cannot repro this on Linux 66.0.3335.0 (Developer Build) (64-bit). Will try Mac later.
,
Jan 30 2018
Cannot repro on Mac 66.0.3334.0 (Official Build) canary (64-bit) either.
,
Jan 30 2018
Rechecked the above issue on Mac OS X(10.12.6,10.13.1) with latest canary chrome version : 66.0.3334.0 and the issue is still reproducible. Note : 1. Freshly launch chrome and perform steps mentioned in description. 2. Sometimes issue is not reproduced at first instance,then clear recorded audit and try re-running Audit second time and see if issue is reproduced. 3. As show in the attached "66.0.3334.0 behavior" video at the first instance issue was not reproducible but after clearing the audits and again performing the steps mentioned in the description we are able to reproduce the issue. Attaching "66.0.3334.0 behavior" screen cast for the same. Thank you.
,
Feb 2 2018
,
Feb 9 2018
Rechecked the above issue on Mac OS X(10.12.6,10.13.1) with latest canary chrome version : 66.0.3344.0 and the issue is fixed.Kindly refer attached screen cast for reference. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rp...@etouch.net
, Jan 24 2018Owner: ssid@chromium.org
Status: Assigned (was: Unconfirmed)