Kudos to Mozilla for tackling a huge pain point (having to learn three sets of dev tools because each browser speaks its own protocol suc...

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 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.

Comments (0)

No comments yet. Start the discussion.

Kudos to Mozilla for tackling a huge pain point (having to learn three sets of dev tools because each browser speaks its own protocol suc...

Tags

Related issues

I guarantee it's a convenience feature.

That isn't really relevant for the tool starting the container.

Why is there no link to the source?

Something I wonder about in this domain is if this is the fault of the language.

Namespace pollution is an annoying problem in Rust.

Currently, no language ports of Timefold Solver are planned.

I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...

Why is there no simple workaround for this?

Kudos to Mozilla for tackling a huge pain point (having to learn three sets of dev tools because each browser speaks its own protocol suc...

Comments (0)