Tridactyl: Consider porting to Chrome

Created on 29 May 2019  路  3Comments  路  Source: tridactyl/tridactyl

None of the core developers are particularly interested in supporting Chrome.

However, it has come to my attention that the Chrome Web Store lets you charge for things. As my favourite fellow fellow from the Isle of Wight would have said, we can correct for the negative externalities of bad font rendering and monopolistic behaviour with an extractive tax that would keep the developers well-fed.

Moving to some polyfill style browser replacement with multiple build targets should also make it easier to support Firefox for Android.

It'd also make supporting Vivaldi easier, which I suspect we/I may have to move to if userChrome dies.

P4 enhancement

Most helpful comment

I'd be able to put a tiny bit of support into it, since I have to use chrome for internal tools at work and it's super annoying.

dollar_dollar_mode smells like victory.

All 3 comments

Also we could have dollar_dollar_mode like neo_mouse_mode, and I think that would make it all worth it.

I'd be able to put a tiny bit of support into it, since I have to use chrome for internal tools at work and it's super annoying.

dollar_dollar_mode smells like victory.

@MatiasStorm asked a while ago if there were other extensions for both Firefox and Chrome.

https://github.com/glacambre/firenvim is an obvious one since glacambre is a Tridactyl developer.

https://github.com/lusakasa/saka-key is like Tridactyl but works on Chrome and Firefox.

https://github.com/philc/vimium also supports both.

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Build_a_cross_browser_extension is full of handy tips.

Was this page helpful?
0 / 5 - 0 ratings