Regression: blank screen in chrome://inspect/#devices
Reported by
pieroba...@gmail.com,
Jan 13 2018
|
||||||||||
Issue description
Chrome Version : 65.0.3315.3
OS Version: OS X 10.13.3
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari: not tested
Firefox: not tested
IE/Edge: not tested
What steps will reproduce the problem?
1. go to chrome://inspect/#devices
2. inspect my app
What is the expected result?
A pop up with my app in it
What happens instead of that?
A blank screen with this error in the devtools :
Uncaught TypeError: InspectorFrontendHost.isUnderTest is not a function
at Object.Host.isUnderTest (inspector.js:914)
at Main.Main._gotPreferences (inspector.js:8194)
at DevToolsAPIImpl.embedderMessageAck (devtools_compatibility.js:33)
at <anonymous>:1:13
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3315.3 Safari/537.36
,
Jan 15 2018
Same problem with Windows when trying to debug a Cordova webview running in Chrome on Android (Pixel / Android 8.1) via the USB connection in Chrome desktop browser (65.0.3319.0 (Offizieller Build) canary (64-Bit)). Attempting to inspect web pages running on the mobile device results in a blank page.
,
Jan 15 2018
,
Jan 16 2018
The problem is from Chrome dev (v65) on smartphone. With original chrome it's ok.
,
Jan 16 2018
Thanks for filing the issue! As the issue seems to be related to debugging/inspecting a device from a machine, which is out of scope for triaging for ET team, hence requesting some one from TE-Hyd team to have a look into this for further investigation. Adding label TE-NeedsTriageFromHYD.
,
Jan 16 2018
I have the same issue here (and it really hurt my productivity!). Inspecting an element on a remote device (whether physical, or emulated), causes the issue. Tested and fails for me in: Version 65.0.3315.4 (Official Build) dev (64-bit) Tested and works for me in: Version 63.0.3239.132 (Official Build) (32-bit)
,
Jan 17 2018
,
Jan 22 2018
,
Jan 22 2018
,
Jan 22 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/bfc020eb4e62925b0cef14fe8e7cc40dd5a8b774 commit bfc020eb4e62925b0cef14fe8e7cc40dd5a8b774 Author: Dmitry Gozman <dgozman@chromium.org> Date: Mon Jan 22 21:26:36 2018 [DevTools] Fix InspectorFrontendHost.isUnderTest not present in newer Chrome We should return false for backward-compatibility with older frontends. Regressed here: https://chromium.googlesource.com/chromium/src/+/baf650e823bb8fd2615e6ec2920b46600d2a7585. Bug: 802928 , 801835 Change-Id: Ibbe3a932467f5c4cb7c6db49bef12f5c10a40926 Reviewed-on: https://chromium-review.googlesource.com/879166 Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org> Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#530999} [modify] https://crrev.com/bfc020eb4e62925b0cef14fe8e7cc40dd5a8b774/third_party/WebKit/Source/devtools/front_end/devtools_compatibility.js
,
Jan 23 2018
Verified the fix on Mac 10.12.6 using latest Chrome version #66.0.3329.0 as per the comment #0. Attaching screenshot for reference. We didn't see any blank screen, we are able to inspect the mobile device. Note: Followed the repro steps as in Issue 802928 (duped in C#8) Hence, the fix is working as expected. Adding the verified labels. Thanks...!!
,
Jan 23 2018
,
Jan 23 2018
,
Jan 23 2018
Approving merge to M65 branch 3325 based on comment #11. Please merge ASAP. Thank you.
,
Jan 23 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9dcedc4b74321032789ab596f57d55999bacdfe3 commit 9dcedc4b74321032789ab596f57d55999bacdfe3 Author: Dmitry Gozman <dgozman@chromium.org> Date: Tue Jan 23 19:03:08 2018 [DevTools] Fix InspectorFrontendHost.isUnderTest not present in newer Chrome We should return false for backward-compatibility with older frontends. Regressed here: https://chromium.googlesource.com/chromium/src/+/baf650e823bb8fd2615e6ec2920b46600d2a7585. TBR=dgozman@chromium.org (cherry picked from commit bfc020eb4e62925b0cef14fe8e7cc40dd5a8b774) Bug: 802928 , 801835 Change-Id: Ibbe3a932467f5c4cb7c6db49bef12f5c10a40926 Reviewed-on: https://chromium-review.googlesource.com/879166 Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org> Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#530999} Reviewed-on: https://chromium-review.googlesource.com/881811 Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/branch-heads/3325@{#33} Cr-Branched-From: bc084a8b5afa3744a74927344e304c02ae54189f-refs/heads/master@{#530369} [modify] https://crrev.com/9dcedc4b74321032789ab596f57d55999bacdfe3/third_party/WebKit/Source/devtools/front_end/devtools_compatibility.js
,
Jan 25 2018
Verified the fix on Mac 10.13.1 Chrome version #65.0.3325.18 as per the comment# 15 Attaching screen shot for reference. Observed that "we are able to inspect the mobile device" Hence, the fix is working as expected. Adding the verified labels. Thanks...!!
,
Jan 25 2018
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by pieroba...@gmail.com
, Jan 15 2018