Re:Polypane – Browser for Developers
by t0astbread on Saturday April 25, 2020 @07:05PM
(#22982447)
Maybe a bit of a weird question but I'm curious: What's the reason behind this being it's own entire browser? Like, if I were given the task of implementing this I would try to avoid creating a new browser (because it sounds like a lot of work). But I know that doing "weird things" like that sometimes causes you to hit a lot more roadblocks than expected and I'm curious to hear the technical story behind this!
[ Parent
| on HN ]
Re:Polypane – Browser for Developers
by reilly3000 on Saturday April 25, 2020 @11:04PM
(#22983992)
I don't tend to think of forking Chromium as a new browser. I imagine that Chrome devtools aren't part of the browser extension API they provide, so creating something would have to start at a lower level.
They are on Firefox at least, I assume Chrome too, there's a Vue devtools extension for example that adds a tab alongside inspect, console, debugger, et al. to give you a sort of Vue-aware 'inspect'.
A browser extension would be the other option, but those are severely limited in what they can do and the regular browser model is not built with multiple panes in mind.
To do everything I want to do (like css media query breakpoint defection) I needed something more low-level.