3 ms·
It could never deploy multi-process with XUL cruft. Then the argument would be that Firefox is too far behind. You can never win everybody.
by AsyncAwait 8y ago
It could never deploy multi-process with XUL cruft. Then the argument would be that Firefox is too far behind. You can never win everybody.
- kevin_thibedeau 8y agoTaking away XUL is not the problem. Leaving users with a crippled replacement is.
- gnomewascool 8y ago"e10s compatible" add-ons were as fully-featured as the "original" XUL add-ons and did not interfere with multi-process at all. For instance, VimFx was e10s compatible and could even run with Firefox Nightly (which allowed "legacy" add-ons), without disabling multi-process, until about Firefox 65(!), without major changes.