4 ms·
Interesting choice to use some sort of proprietary OS scripting language instead of just writing a standard WebExtension, I thought. Presumably chrome.tabs.quer
by lol768 5y ago
Interesting choice to use some sort of proprietary OS scripting language instead of just writing a standard WebExtension, I thought. Presumably chrome.tabs.query would have returned all tabs and a native manifest would've allowed comms with the outside world to build a HTTP server. Still, I suppose the approach taken by the author worked at the end of the day - just not very portable.
- somehnacct3757 5y agoYeah I think the web extension approach is the best one. Shame they ruled it out. Extension background scripts can push data wherever you want. You can sideload the extension and talk to localhost ports or anyone on the internet. Use ajax or native events to talk to a local process. There's even an event system that tells you when tabs are opened, closed, activated, deactivated, etc.
- rjbs 5y agoThanks, I'll have a look at writing a web extension, sometime. It sounds like they might not be such a pain, after all. Here, I just forged forward with what I already knew I could get done while goofing off on the weekend.