Remote Debugging not working for inspecting mobile styles

1,919 views
Skip to first unread message

tim9...@gmail.com

unread,
Jan 21, 2015, 12:54:37 PM1/21/15
to google-chrome-...@googlegroups.com
I've noticed many times when using Chrome Inspect for web development that I can't get the right side (where the styles are displayed) to change when I click on different elements on the left side (the html).  I usually refresh or close and reopen the browser to get it 'un-stuck' from the current element.

Now, I'm seeing this when using mobile inspect (via the Android SDK).  It doesn't matter what element is highlighted... I can't change it!  Even if I don't select anything, the <body> element is selected by default and I can't change it to another element.  What can I do here?  Is it a bug?  I have to get back to working on mobile sites.  I can use a 3rd party plugin for replacing Chrome inspect for regular web pages, but for mobile, I have no choice.. it just doesn't work. 

Andrey Lushnikov

unread,
Jan 22, 2015, 4:44:33 AM1/22/15
to google-chrome-...@googlegroups.com
Hi,
Could you please file a bug on crbug.com/new and file a link on it here?

On Wed Jan 21 2015 at 8:54:40 PM <tim9...@gmail.com> wrote:
I've noticed many times when using Chrome Inspect for web development that I can't get the right side (where the styles are displayed) to change when I click on different elements on the left side (the html).  I usually refresh or close and reopen the browser to get it 'un-stuck' from the current element.

Now, I'm seeing this when using mobile inspect (via the Android SDK).  It doesn't matter what element is highlighted... I can't change it!  Even if I don't select anything, the <body> element is selected by default and I can't change it to another element.  What can I do here?  Is it a bug?  I have to get back to working on mobile sites.  I can use a 3rd party plugin for replacing Chrome inspect for regular web pages, but for mobile, I have no choice.. it just doesn't work. 

--
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/9310e0eb-9546-4ed3-94a7-c9ea8e03c409%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ja...@ldrinteractive.com

unread,
Jan 28, 2015, 4:13:24 PM1/28/15
to google-chrome-...@googlegroups.com, tim9...@gmail.com
I'm having this exact bug after upgrading to Chrome 40.0.2214.93 (64-bit) on Linux Mint Debian Edition.  This previously worked fine, but now I can't select any elements in the Dev Tools on a Remote Debugging session to my Cordova app running on my device.

Note that debugging a mobile Chrome tab on the device, and debugging a regular web page, do not show this issue.  It seems to only happen when debugging a WebView.  It's as if the click event on the element in the Dev Tools isn't being registered.

Hmm... upon inspecting the inspector (Inception!), I get the following upon clicking an element in the original inspector:

Uncaught TypeError: undefined is not a function (inspector.js:696)

Appears to be within TreeElement.prototype.isEventWithinDisclosureTriangle.  If I alter this function to return false; before anything else, on-click functionality to the original inspector is restored for that window (though the "disclosure triangles" don't work).

This appears to be a bug.  I will file.

Vsevolod Vlasov

unread,
Jan 29, 2015, 11:07:35 AM1/29/15
to Google Chrome Developer Tools, tim9...@gmail.com
When you file a bug please provide a stack trace as well and copy the particular line where this happens (isEventWithinDisclosureTriangle method is quite long)

--
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.

tjohn...@gmail.com

unread,
Jan 29, 2015, 12:08:51 PM1/29/15
to google-chrome-...@googlegroups.com, tim9...@gmail.com, ja...@ldrinteractive.com
Glad I'm not the only one.... misery loves company haha.  Your situation matches mine to a T.  The only thing I can add is that It's also a problem with Canary (which I believe is also 64 bit).

Josef Mokrý

unread,
Dec 5, 2019, 3:20:52 AM12/5/19
to Chrome DevTools
I have same problem, now on version 78.0.3904.108

Yang Guo

unread,
Dec 5, 2019, 3:56:46 AM12/5/19
to Google Chrome Developer Tools
Can you please file a bug at crbug.com, ideally with precise repro instructions? Thanks!

Yang

--
You received this message because you are subscribed to the Google Groups "Chrome DevTools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages