Extension Support

[falchion10]

I think everyone can agree with me that extension support is basically what's keeping users away from switching to other WebKit browsers that aren't Safari. Every other WebKit browser tries to get Chrome or Firefox extensions working but they all fail to get the majority of them working, probably due to pretty challenging reasons. Is there a way to get native Safari extensions from the Mac App Store working with Nook? This is really the only way to get good quality extensions that people actually know will work on other WebKit browsers. Trying to do the whole Chrome/Firefox extension game isn't going to work, it's already been tried with browsers like Orion.

[jonathancaudill]

Agreed. Interesting take you have about native safari extensions. To be honest I haven't considered it at all, but I'm sure it would be possible.

To be honest, the chrome/firefox extension game has proven to work fairly well for orion. We actually already have some tooling in place and basic features working.

Problem is that web extensions have an insane number of APIs so hooking all those up is labor-intensive, even with the WKWebExtension class we're taking advantage of.

I'll look into safari extensions. Basically we'd have to ask the user for access to the Safari app contents and then copy over the extension code. Which is kinda roundabout. In addition, last I checked (which was a while ago (will do more research!)), safari extensions weren't natively droppable into WKWebView. Still needed the same hookups and tooling with WKWebExtension.

Will look into this further. This is a really high priority for us too!

[jonathancaudill]

much progress has been made @falchion10 , in particular importing safari extensions has been quite helpful/useful for me. Obviously not all of them work yet!