New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 843276 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 829884
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Inspect attribute not working

Reported by wrbe...@gmail.com, May 15 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

Steps to reproduce the problem:
1. Inspect Element
2. Refresh browser leaving developer tools open
3. Inspect Element again

What is the expected behavior?
It should show the html in dev tools and allow me to inspect the element.

What went wrong?
Inspect goes to body element and will not permit deeper inspection. Dev tools has to be closed and inspect element used again before the html in the body will appear.

Did this work before? Yes 65

Chrome version: 66.0.3359.139  Channel: n/a
OS Version: 10.0
Flash Version:
 
Labels: Needs-Bisect Needs-Triage-M66
Cc: krajshree@chromium.org
Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue on Win-10 using chrome reported version #66.0.3359.139, latest stable #66.0.3359.181 and latest canary #68.0.3431.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Inspected Element
2. Refreshed browser leaving developer tools open
3. Inspected Element again.
4. Observed that it showed the html in dev tools and allowed to inspect the element as expected.

wrbeggs@ - Could you please check the attached screen cast and please let us know if anything missed from our end. Also please check the issue on latest canary #68.0.3431.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!
843276.mp4
4.7 MB View Download

Comment 3 by vebru...@gmail.com, May 18 2018

User Agent:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.170 Safari/537.36

Steps to reproduce problem:
* Open new tab
* Open devtools
* Go to a website in which a lot of ajax is happening
* Inspect a random element
* Devtools Elements panel shows part of the DOM, but the body element remains visually empty

Expected
* Body element shows rest of DOM-tree, especially the inspected element

What went wrong
* Devtools doesn't show DOM elements which are contained by the body

Did this work before? Yes in 65

Chrome version: Checked both Version 66.0.3359.170 (Official Build) (64-bit) and Version 66.0.3359.181 (Official Build) (64-bit)
OS: Mac Sierra 10.12.6
devtools-elements-panel-body-appears-empty.mov
20.4 MB Download

Comment 4 by vebru...@gmail.com, May 18 2018

Ah btw, I've verified this in "Version 68.0.3434.0 (Official Build) canary (64-bit)" and I am not able to reproduce it there.

Comment 5 by woxxom@gmail.com, May 18 2018

Looks like  bug 829884  fixed in Chrome 67 (currently beta).
Mergedinto: 829884
Status: Duplicate (was: Unconfirmed)
Thanks for filing an issue! Should be fixed in next Chrome update.

Sign in to add a comment