Replies: 1 comment
-
Tridactyl could work fine in Chrome (at least under manifest V2 which is end-of-life, but we'll need to port to manifest V3 at some point anyway for Firefox). The blocker is that the small differences in the APIs between Firefox and Chrome - like the fact that Chrome doesn't have tab containers - mean that minor things that Tridactyl expects to exist don't, which then error out and stop the whole extension from working. The solution I would like is for our tests to check that we are using APIs in a way that is safe for all the browsers we target. That should be easy because all the individual bits we need to do that already exist, it is just a case of wiring them up properly. But so far I have not managed to do it. There's more info on this issue - #1619 |
Beta Was this translation helpful? Give feedback.
-
Just wondering.
Decided to ask here, as many of you know the code-base of this project well. I just have been using this extension for years.
Chrome has a way, way bigger "market" share, currently, and most extensions which work on Chrome also work on Edge (I know... that's probably not the target audience...)
Something tells me that perhaps Google has made Chrome less mod-able, and this extension rather needs to change a lot browser-UI side?
Beta Was this translation helpful? Give feedback.
All reactions