3 ms·

or just click the gear and popup the devtool in its own window.

• joshstrange 11y ago
  You're missing the point. This is about pulling out devtools so that it can be used with more than just chrome and provide a single way to debug everything from FF/Chrome/Safari to NodeJS apps and iPhone native apps.
  • glandium 11y ago
    Note you can already do most of that with Firefox's Devtools: https://developer.mozilla.org/en/docs/Tools/Remote_Debugging https://developer.mozilla.org/en/docs/Tools/Remote_Debugging
    • josteink 11y ago
      That may be, but as you read the article, you do get re-inforced the idea that WebKit (and by proxy Chrome DevTools) are infinitely more embeddable and mallable: All examples listed of non-standard usage are WebKit and Chrome. Not a single Firefox or Mozilla component in sight. Is there a (still) technical reason for this, or is it just that WebKit & Chrome won the developer mindshare to the point where there's point in investing elsewhere if you want to get picked up? If so, that would have me worried. You may argue it's "only" on the developer-side, but that's always where things start out before they spread out. We are already very close to a Chrome monoculture taking hold, and I find websites and services on a daily basis which doesn't work in Firefox (or Firefox mobile) which I have to open in Chrome in order to have loading correctly. I think we're already at the point Microsoft was with IE, if not well beyond. As someone who cares about the open web, open data and a proper standards-based internet, I think pretty much everything is heading in the wrong direction these days.