3 ms·
Kudos to Mozilla for tackling a huge pain point (having to learn three sets of dev tools because each browser speaks its own protocol sucks). I'm most familiar
by bsimpson 12y ago
Kudos to Mozilla for tackling a huge pain point (having to learn three sets of dev tools because each browser speaks its own protocol sucks).
I'm most familiar with the WebKit/Chrome Dev Tools, and found this awesome project via Mozilla's post:
https://github.com/google/ios-webkit-debug-proxy https://github.com/google/ios-webkit-debug-proxy
If it works as advertised, it'll let you connect to iOS browsers from Chrome Dev Tools. Honestly, I'm surprised they don't have a version of this compiled into Chrome for iOS.
- bsimpson 12y agoUnfortunately, I couldn't get it to work: https://github.com/google/ios-webkit-debug-proxy/issues/72 https://github.com/google/ios-webkit-debug-proxy/issues/72
- joshschreuder 12y agoIf you're on Windows I've been able to do this with Telerik's AppBuilder (http://docs.telerik.com/platform/appbuilder/debugging-your-code/debugging-on-device/prerequisites-for-debugging#ios-requirements http://docs.telerik.com/platform/appbuilder/debugging-your-c...) It opens up a Webkit Dev Tools that are pretty close to the latest Chrome version and lets you interact with Safari on iOS. Even highlights elements the same as desktop.
- thejosh 12y agoHave you tried Weinre?