First, it's amazing that it's there. It solved A LOT of my problems. I use it every time I need to access tab's js context to print something to the console, get window.performance numbers or add listeners there.
I ended up doing it about twenty times.
I just noticed this:
The list goes on like that for a few pages...
Looks like every time I use it, it creates a new frame?
Thaaaat's... not healthy, right?
uh... So a way to avoid it would be what? inject all my tab functions via the content-script by modifying dom. Deploy a listener there for my extension to send messages to the tab, then instead of running functions directly, run them through this awkward construct?
Gosh this sounds like such a drag. I don't wanna do it. Why don't they have an api simplifying it. This whole awkward logic could definitely be consumed and optimized by chrome.
It's a lot of work to do it at this time. And the benefit seems to be miniscule. What do you think? Maybe there are better ways of mitigate this or maybe no mitigation is required. I don't like to see all these frames for sure.