Inspector, inspected element not kept highlighted after reload

Birger Fühne

unread,

Aug 12, 2016, 5:15:56 PM8/12/16

to Google Chrome Developer Tools

Anyone else noticed this?

Expected:

Inspecting an element and reloading the page used to keep the element selected in inspector, which is very helpful during debugging sessions.

Situation now:

Inspect an element. Reload the page. The inspector jumps to <body>

Is this change intended? Please revert, adds a lot of hassle during debugging.

Version: 52.0.2743.116 (64-bit) on MacOS and Win10

PhistucK

unread,

Aug 12, 2016, 7:14:47 PM8/12/16

to Google Chrome Developer Tools

If your element is created (or appended) dynamically, the Developer Tools feature cannot get back to it after a reload, probably because it tries to do it too fast.

Is it possible that the said page switched to create (or append) that element dynamically?

For trying it too fast and failing and not trying again, you can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/5b8bbdd9-0f8c-45d9-8d5a-c4dcebe064e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Alexander Kuales

unread,

Aug 13, 2016, 5:56:55 AM8/13/16

to Google Chrome Developer Tools

I am struggling with this issue as well during developing.

For testing purposes I created a blank webstarterkit-environment ( - no element injecting/appending) and it could not keep dom-children highlighted after reload .

That was until I removed all script/link-requests.. Having only a medium-sized HTML-Tree (no scripts, no styling) the inspector could always jump to an inner-child (otherwise it would always jump to <body />, even when all requested files were empty).

Issue appers on both mac und win10 with latest Chrome-Version 52.0.2743.116. (no extensions installed, private and normal mode)

Also, I openend an angular-driven Site on localhost on a Chrome v50.x on an older mac and the inspector would always jump to the selected element after reload - as expected. This correct behavior stopped as soon as I updated Chrome to latest version.

I couldn't find a new issue at crbug.com yet, did you already file one (@BirgerFühne)?

Reply all

Reply to author

Forward