New issue
Advanced search Search tips

Issue 913484 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Element Inspector not working when inspecting a Remote Device

Reported by c...@shipt.com, Dec 10

Issue description

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

Steps to reproduce the problem:
1. Download an apk for a webview app to a mobile device
2. In DevTools open "Remote Devices" tab
3. Inspect the webview app on the mobile device
4. Turn on "Element Inspector" on the top left of the devTools page
5. Hover over elements on the screen with your mouse on the preview

What is the expected behavior?
Just like within a normal website, when your mouse hovers over a web element on the preview screen, it appears highlighted in the "Elements" tab on DevTools page.

What went wrong?
It is no longer highlighting the correct elements. It looks like it's z-index is off.

Did this work before? Yes 69

Chrome version: 70.0.3538.110  Channel: n/a
OS Version: OS X 10.14.1
Flash Version:
 
Owner: l...@chromium.org
Labels: Needs-Bisect Needs-Triage-M70
Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET Needs-triage-Mobile OS-Android
Thanks for filing the issue!

As the issue seems to be triaged using an Android device, hence adding appropriate labels for further inputs from respective team.
Labels: Needs-Feedback
Thanks for the report.  Could you please let us know
- The Android Webview version?
- Does this bug happen if you inspect pages running on mobile Chrome?
- Is nothing on the page getting highlight at all?  Or does the highlight appear, just not in the correct location?
Hey there! It often doesn't show anything on the elements page. If you scroll over the individual elements over the Elements Tab, then it will highlight elements as if they were all smashed to the top of the page.
image.png
33.3 KB View Download
Project Member

Comment 6 by sheriffbot@chromium.org, Dec 17

Cc: l...@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
Sorry it took so long to get back!
Any progress on this?
Labels: Needs-Feedback
Status: Assigned (was: Unconfirmed)
I can reproduce similar issues when inspecting a page in Chrome-for-Android-71.0.3578.99.  DevTools and chrome://inspect use specific frontend versions that target the Chrome version running on Android.

Interestingly, picking an element seems to work perfectly if I use the up-to-date frontend (73.0.3660.0) for debugging.

OP: could you please try these steps and let us know if the highlights work?

- Install Chrome Canary (73+)
- Go to "chrome://inspect", wait for the list of targets to appear
- Open DevTools on this page
- In the Console, run this command:
sendCommand = function(_, args) { chrome.send('inspect-fallback', Array.prototype.slice.call(arguments, 1)) };
- Click the "inspect" link to debug the webview on your device

If these steps above fix the behavior, we can consider showing an "inspect fallback" option in the list all the time.
Those steps worked!
Hi there, tested here with Google Chrome 73.0.3664.3 dev, those steps make the inspect feature work again.

But I still cannot interact with the app, clicks do not trigger event handlers on elements (trigger via the element's click method works). 
Labels: -Needs-Feedback
c#11, click interactions work for me.
- Could you please check a few different sites to see if clicks fail everywhere? 
 If it's a specific site, is there a public link you could send us to reproduce?
- What is the version of Chrome running on the device?  If it's too outdated, it's likely that we had bugs in older versions that were fixed since then, and a more up-to-date mobile Chrome/Webview version should work.
The Chrome version on android is 71.0.3578.99

I'm debugging an Android app with an embedded webview (built on cordova).
click interactions work when debugging a Chrome tab, but not when I debug the cordova app.

What happens after further testing:

When the app is open, clicks work fine on the Android device.
I open the debug view, clicks on the device do nothing.
But if I click on the screencast view, the preceding click events are fired (the more I keep the mouse button down while moving over the button, the more events are fired from the previous clicks on the device).
After that, clicking on the screencast view has no effect.

Comment 14 by chelamcherla@chromium.org, Jan 17 (5 days ago)

Cc: chelamcherla@chromium.org
Labels: Triaged-Mobile Needs-Feedback
@julien.le-bras: Please provide sample app and screencast of the issue, this would help in further triaging.

@luoe: Does information in C#13 helpful. Please help in triaging the issue.

Thanks!

Comment 15 by l...@chromium.org, Jan 18 (5 days ago)

Cc: santhoshkumar@chromium.org
 Issue 920533  has been merged into this issue.

Comment 16 by umesh1...@gmail.com, Jan 18 (4 days ago)

#9 is doesn't work for me. There is some progress with this that i was able to interact with elements but selected element was not selected but the nearby element which still makes it unusable, click event also don't work. checked with the latest canary build( Version 73.0.3674.1) and on my mobile chrome android version (71.0.3578.99)

This can be an issue with the chrome android also as i have also tried to install few older versions of chrome desktop from chrome 57 to 65. It still doesn't work in those too. But my mobile's chrome browser is the latest version.

I will try to downgrade the android version also and revert back it that works.

Thanks!

Comment 17 by umesh1...@gmail.com, Jan 18 (4 days ago)

Hello Again!

I downgraded my android webview to version 60 and everything start working fine, the element selection via inspector and click event with mouse. I don't think there is any problem with Chrome Desktop, the real problem lies in the android webview.

PS: I uninstalled the android webview from google play, then downloaded older version (60) after that installed it via adb shell.


Thanks!

Sign in to add a comment