One of the reason Brave finally forked Chrome (they went from gecko based, to electron based, to chrome fork) was to not suffer from the Web Compatibility issues that Firefox has.
Not too familiar with the "Web Compatibility" issues firefox has, but that would have been from when they moved off gecko at least, i doubt that was the case from using electrons chromium fork to upstream chromium. I wonder if they'd consider servo or would be too much work for them at this point?
This[0] says they started off with electron pre dec-2018, nothing about gecko.
Electron uses Chromium, so as Fabrice noted, our reasons for moving off our fork of Electron were unrelated to the prior move from Gecko to Chromium/Blink.
Electron's architecture is insecure by default in too many ways, even if one enables the Chromium Sandbox (which was off by default at least when we used Electron).
> unrelated to the prior move from Gecko to Chromium/Blink
Is there publicly available reason for this move? No worries if there isn't.
No plans on forking from ff v ~70-ish with the servo stuff and going with the rust stuff or just more with chromium? Too much work and not worth it at this point or other tradeoffs? I like a lot of stuff you have been doing with brave (use the default search instead of ddg now in my ff fork) and wish some of it was in ff without me personally having to do it xD
We couldn't even get HTML5 DRM for Gecko-based Brave, never mind a ton of other webcompat problems vs. Chromium/Blink. We did a full spreadsheet and the winner was very clear. This is a reflection of Google's market power, in large part, but it is what it is.
This[0] says they started off with electron pre dec-2018, nothing about gecko.
[0] https://en.wikipedia.org/wiki/Brave_(web_browser)#History