New issue
Advanced search Search tips

Issue 793814 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Remote Debug of Chromium Ver. 44 based apps (Xwalk) not working anymore

Reported by pri...@gmail.com, Dec 11 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36

Steps to reproduce the problem:
1. Run APK with XWalk ver. 15 (Chromium 44) on Android 4.4
2. Remote Inspect results in mangled output, borderless windows, menu without items
3. Same APK but on Android 5.0 (Webview) can be debugged perfectly.

What is the expected behavior?
Chrome Inspector should work on legacy Chromium 

What went wrong?
After updating to Chrome 63 the chrome inspector fails to work correctly when the remote chrome is an older version (in this case XWalk v.15 based on Chromium 44). 

Those are industrial devices (point of sales) with a custom software and with this change we cannot debug issues anymore. 

Did this work before? N/A 

Chrome version: 63.0.3239.84  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 

Comment 1 by pri...@gmail.com, Dec 11 2017

The user Agent reported by the Chromium 44 embedded in the APK is: 

"Mozilla/5.0 (Linux; Android 4.4.3; TC700H Build/01-23257-K-18-03-00-MV) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Crosswalk/15.44.384.13 Mobile Safari/537.36"

Could you open up DevTools on DevTools? Once you've done the usual remote debugging steps, you can open up a DevTools inspecting the DevTools front-end by undocking DevTools and then doing (ctrl/cmd+shift+i). Once you do this, could you report any console / network errors that you see? Also, what version of Chrome were you using before (62?)?

We try to be careful and preserve backwards compatibility but it's possible 63 removed a Chrome/Blink API that we used to rely on in historical DevTools front-ends.
Labels: Needs-Feedback Needs-Triage-M63
Labels: -Pri-2 Pri-3

Comment 5 by pri...@gmail.com, Dec 12 2017

It was working up to version 62. I also attached a file showing how the devtools look like when trying to connect to a Remote chromium 44.

I cleared the dev-tool cache and tried a location.reload(). No network errors but this console messages: 

========================================================================
[Deprecation] Use of the Application Cache is deprecated on insecure origins. Support will be removed in the future. You should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.
inspector.html:1 Creating Application Cache with manifest chrome-devtools://devtools/remote/serve_rev/@200670/200670.manifest
inspector.html:1 Application Cache Checking event
inspector.html:1 Application Cache Downloading event
inspector.html:1 Application Cache Progress event (0 of 103) chrome-devtools://devtools/remote/serve_rev/@200670/Images/chromeRight.png
inspector.html:1 Application Cache Progress event (1 of 103) chrome-devtools://devtools/remote/serve_rev/@200670/Images/errorWave.png
[Deprecation] /deep/ combinator is no longer supported in CSS dynamic profile.It is now effectively no-op, acting as if it were a descendant combinator. /deep/ combinator will be removed, and will be invalid at M65. You should remove it. See https://www.chromestatus.com/features/4964279606312960 for more details.
inspector.html:1 Application Cache Progress event (2 of 103) chrome-devtools://devtools/remote/serve_rev/@200670/layers_module.js
inspector.html:1 Application Cache Progress event (3 of 103) chrome-devtools://devtools/remote/serve_rev/@200670/Images/toolbarButtonGlyphs.png
inspector.html:1 
.....
Application Cache Progress event (103 of 103) 
inspector.html:1 Application Cache Cached event

I will try playing with the '--disable-blink-features=DeepCombinatorInCSSDynamicProfile' and/or
'--disable-blink-features=ShadowPseudoElementInCSSDynamicProfile' switches if this makes a difference.

devrools.PNG
130 KB View Download

Comment 6 by pri...@gmail.com, Dec 12 2017

Update: it is the "DeepCombinator" issue. 

Running chrome with 

.\chrome.exe --enable-blink-features=DeepCombinatorInCSSDynamicProfile

completely restore the functionality to the devtools. 

I will report on the other thread of this behavior. 

Cc: pfeldman@chromium.org
Status: WontFix (was: Unconfirmed)
@prinex - thanks for following up. Unfortunately, there isn't a lot our team can do since Blink (the rendering engine) has deprecated and will remove the deep selector. There's a range of historical front-ends where we used this prior to its deprecation and it looks like they will be broken on any up-to-date Chrome.

It's very risky for us to change these historical front-ends and swap out usage of the deep API, so the only solution / hack I can think of is to use an older Chromium build, as these don't automatically upgrade like normal Chrome builds. You can find steps for this: https://www.chromium.org/getting-involved/download-chromium

@pfeldman - is there any workaround that you can think of?
Cc: paulir...@chromium.org
 Issue 803213  has been merged into this issue.

Sign in to add a comment