Chrome Developer Tools 63 breaks remote debugging with older Xwalk Version

[Matteo Prinetti]

We have Cordova based  apps that use XWalk rel 15 (based on Chromium 44) on Android 4.4 Devices (those app cannot run on the local webview as it is too old). 

Since updating to Ver 63 we cannot remote debug anymore. 

What happens is - invoking the remote inspector brings up a mangled view with only partial functionality (see attachment).

Same APK but on Android 5.0 (and without XWalk) can be debugged remotely.

Question: has been support for older Chromium Version (in this case Chromium 44) been removed from Dev Tools ? This is a big issue as we have over 8000 Point of Sales running on this solution that cannot be debugged anymore.

[Pavel Feldman]

The issue is the /deep/ selector that is no longer working in Chrome that was used in DevTools M44. In order to workaround this, you might have to use Chrome prior to M63 to remote debug your app. You should be able to find Chromium of previous versions for all the platforms. Sorry about the inconvenience, but /deep/ removal was a breaking change we could not do anything about.

--
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-developer-tools+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/7ea8f5ee-f38f-42b1-a7d1-53fa70ad77a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chris VDB]

 

I have the same problem when debugging Adobe extensions. When the devtools opens, console logs are appearing but I cannot scroll through them. No scroll bars appear, keyboard scrolling also does not work. So any messages that go off-screen are inaccessible. Also the other panels come up but do not behave as expected. I cannot resize them or scroll through. The settings panel is also broken, It opens, but no content appears.

 

Adobe uses a Chromium-based embedded browser, and the devtools worked fine until the upgrade to version 64

I now downgraded to version 61 and devtools works fine again. I had to disable the auto-updating tool and ignore lots of NOT RECOMMENDED warnings.

Chrome is my default web browser, so I'm afraid for security issues.

I understand it has to do with removal of an old API, I hope the devtools can be adapted to a new API soon. 

Chris