Remote Debugging - Inspector Window gets Stuck on Element

tjohn...@gmail.com

unread,

Jan 20, 2015, 6:30:03 PM1/20/15

to google-chrome-...@googlegroups.com

This happens occasionally when just inspecting a regular web page. But now it happens 100% of the time when inspecting mobile styles via remote debugging. Once you open mobile debugging, the <body> element is highlighted. Clicking on another element inside the <body> used to highlight that element and display the styles on the right side for the new element. It now gets 'stuck' on whatever element is highlighted. You can click on the little arrow (to pick an element), then touch that element on the mobile device and it will highlight it in the dev tools window. But, again, it is stuck. If you want to view the styles of a sub-element, you can not.

What I've tried:

I updated the SDK.

I disabled ALL chrome extensions.

I installed Chrome Canary and tried that.

For now, until this is fixed, Dev Tools is 100% useless to me.

Andrey Lushnikov

unread,

Jan 22, 2015, 4:51:45 AM1/22/15

to google-chrome-...@googlegroups.com

This is a bug. Please, file it on crbug.com/new with information about your chrome version, and post a link here.

--
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-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/7087cc46-6b02-4ebd-982e-631c983d44fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

tjohn...@gmail.com

unread,

Jan 22, 2015, 12:01:25 PM1/22/15

to google-chrome-...@googlegroups.com, lush...@chromium.org

Now, maybe I should hold off. I've not wanted to update Windows from 8 to 8.1 for a few years now. But in the past week, I've been prompted daily to upgrade and my machine has been running very slow ever since the update prompts so I said F it yesterday and upgraded. And I decided to try it again before posting the bug report and it seems to be working fine now. Don't know if it's from the upgrade or if the developers found and fixed it already. But either way, it's working today. yay!

David Pickthorn

unread,

Jun 4, 2018, 4:27:49 PM6/4/18

to Chrome DevTools

Same issue, so frustrating. Any patches or solutions come out yet?

fakrurazie...@gmail.com

unread,

Feb 13, 2019, 3:36:40 AM2/13/19

to Chrome DevTools

Same issues too. any updates?

Reply all

Reply to author

Forward