WebExtensions support?

[alexherbo2]

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions

[bqv]

https://webkitgtk.org/reference/webkit2gtk/stable/WebKitWebExtension.html

[aartaka]

https://webkitgtk.org/reference/webkit2gtk/stable/WebKitWebExtension.html

Unfortunately, WebKitWebExtension is not related to the WebExtensions API. WebKit only supports extensions written in C.

[aartaka]

However, there's this attempt to use Python for extension-writing. We can follow this approach of thin C adapters and write lisp on top of them or call lisp-urls from these adapters to talk with Lisp-side (I'm not sure it's possible now, but, if we'll root lisp-url deeper into WebKit, it can become possible).

Even more work should be done to enable full WebExtensions API, though. As discussed with @Ambrevar, we'll need a JS library to handle the WebExtensions API.

[bqv]

I see, my mistake

[toothbrush]

This looks like an amazing browser initiative and i'm super excited to try it out! For me having uMatrix (or uMatrix functionality) is a hard requirement though so i'm very keen to hear how WebExtension support is progressing 😺 I don't want to be an entitled freeloader, just asking out of interest 🙏

All the best!

[oxysoft]

Nyxt looks like a competitor to qutebrowser right now, so having it before qutebrowser could be a big advantage!

[bqv]

I imagine they're more interested in lisp-based extensions than traditional ones, tbh. I would see if it's possible to implement the functionality you're after in clisp right now

[aartaka]

I imagine they're more interested in lisp-based extensions than traditional ones, tbh.

Not really. While lispy extensions are cool, competing with popular extensions (like uMatrix, uBlock Origin, Dark Reader -- you name it) is an uphill battle. Supporting WebExtensions API is still a high-priority task, it's just that we cannot do everything at once :)

[whirm]

I imagine they're more interested in lisp-based extensions than traditional ones, tbh.

Not really. While lispy extensions are cool, competing with popular extensions (like uMatrix, uBlock Origin, Dark Reader -- you name it) is an uphill battle. Supporting WebExtensions API is still a high-priority task, it's just that we cannot do everything at once :)

Excuses for the noise but is there a feature roadmap (other than the 2.0 tag) to get a rough idea of when this is coming? Thanks for this amazing project, really looking forward to use it!

[bqv]

Honestly with extensions going the way they are, I think I'd prefer lispy extensions to standards-compliant stuff. Let's make a difference

[Ambrevar]

Elric Milon <[email protected]> writes:

Excuses for the noise but is there a feature roadmap (other than the 2.0 tag) to get a rough idea of when this is coming? Thanks for this amazing project, really looking forward to use it!

Thanks for the kind words! Sorry, there is no roadmap beside the issue tracker and the ChangeLog which has a few "future tasks". All I can say is that the minibuffer overhaul (#777) and the renderer overhaul (possibly with WebEngine support) have higher priority, but WebExtensions should not be too far off after that. Contributions are welcome!

[aadcg]

Closing since it's a duplicate of #2875.