Older version of the Chrome inspector doesn't work in Chrome 54

[lexs]

KeyboardEvent.keyIdentifier was removed in Chrome 54 but is used in old version of the inspector that iwdp uses. This means that the console no longer works as the enter key isn't recognized.

We'll need an modified version that replaces all uses of KeyboardEvent.keyIdentifier with KeyboardEvent.key.

[MarisaLovesUsAll]

Confirm.
Staying with google-chrome 53 for now.

[code-tree]

Any chance of this being fixed?

[artygus]

The purpose of the tool is to proxy requests to safari devtools through websocket protocol. If you're using linux or windows you could use devtools extracted from webkit https://github.com/artygus/webkit-webinspector. If you don't like webkit devtools you could stick to valence from mozilla or similar projects.

[auchenberg]

You can use https://github.com/RemoteDebug/remotedebug-ios-webkit-adapter to enable newer versions of the Chrome DevTools front-end.

[lexs]

@artygus The readme only mentions the Chrome inspector (which, while based on Webkit) is currently broken. The version specified here doesn't work anymore:

ios-webkit-debug-proxy/src/ios_webkit_debug_proxy_main.c

Line 210 in dcaa139

const char *DEFAULT_FRONTEND =

Please reopen this until that is fixed (or you recommend to use @auchenberg's adapter for example).

[artygus]

@lexs good catch

[code-tree]

@auchenberg that appears to require iTunes which isn't available on Linux. Any other options to resolve this? Even on Chrome 53 I can't select elements (can only expand them).

[artygus]

@code-tree it doesn't require iTunes, usbmuxd should be sufficient. You could also use devtools frontend from webkit sources

[auchenberg]

@code-tree The adapter hasn't been tested in Unix, but feel free to open a PR with the changes needed. Sounds like it's pretty straightforward.

[artygus]

the alternatives were added to readme 4b940e6