As the original author of GtkMozEmbed I'd like to say that this is way too little, way to late. Mozilla has historically been very much against anyone trying to use the engine in anything other than the firefox app.

This is completely up to them of course, and it probably let them move firefox forward faster, due to not having to care about APIs. However, it also means that chrome completely took over the entire market with electron and similar things.

Yeah, the Sailfish OS project, which is an operating system for mobile devices. They use Gecko as engine for their default web browser, but are always lagging with engine updates as every time they have to painstakingly rebase all of their embedding patches on top of the new Gecko codebase.

smnthermes

Why do they not use the ESR version?

m4rtink

I think they do, just an old one as ESR AFAIK does not guarantee you stability of the internal APIS needed for embedding between ESR versions.

I think it's at least 45 ESR, as mentioned in release notes ~year ago: https://blog.jolla.com/hossa/

There is an issue tracking the Gecko update on the community discussion/bug reporting tool used for Sailfish OS: https://together.jolla.com/question/133621/update-gecko-in-t...

The source of the Sailfish OS browser lives here: https://github.com/sailfishos/sailfish-browser

(Even though Sailfish OS is sadly not fully open source, the browser is as are other core applications and frameworks.)