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

Issue 848706 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Reveal DOM node on hover just stops working

Reported by nige.ani...@gmail.com, Jun 1 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.56 Safari/537.36

Steps to reproduce the problem:
1. Debug a complex, dynamic UI

What is the expected behavior?
When you hover a DOM node in the "Elements" tab, or the value of a var which references a DOM node, or a DOM node that's logged on the console, you should see a highlight.

This just randomly STOPS happening. It's VERY annoying and VERY inconvenient for debugging.

What went wrong?
It doesn't highlight the hovered node.

Did this work before? N/A 

Chrome version: 67.0.3396.56  Channel: n/a
OS Version: OS X 10.13.4
Flash Version:
 
Labels: Needs-Feedback
It does not seem to be possible to reproduce this issue. Do you see it when working on a simple web page? Can you try using a new Chrome profile w/o any extensions installed?

Comment 2 Deleted

Labels: Needs-Triage-M67
As seen here, it just completely quits painting. I switched tabs to go back to this ticket because it was annoying me that I could not hover to see the bounds of my element, and when I returned to the tab, I could not see anything!
Screen Shot 2018-06-05 at 12.37.47.png
793 KB View Download
Project Member

Comment 5 by sheriffbot@chromium.org, Jun 5 2018

Cc: eostroukhov@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by l...@chromium.org, Jun 11 2018

Labels: Needs-Feedback
Thanks for the screenshot.  Unfortunately, we need more information to be able to reproduce and investigate.

Could you please check DevTools on DevTools and see if there are any Console errors?
https://stackoverflow.com/questions/12291138/how-do-you-inspect-the-web-inspector-in-chrome/12291163#12291163

Are there any steps or other conditions before it stops working?

Do you happen to have a JSFiddle or some publicly available site that consistently reproduces this bug?
Status: Archived (was: Unconfirmed)
Well, I'll have to switch to Firefox. Chrome's debugger, while getting ever more sophisticated is acquiring more deep, intermittent bugs which cannot be reproduced in a simple HTML document.

I have to keep track of dozens of elements being dragged around, and if I can't *SEE WHERE THEY ARE*, the debugger is not no use at all.

Sign in to add a comment