4 ms·

Couldn't they just do something similar to Microsoft's Edge/IE11 approach? Servo for HTML5+/CSS3+/Javascript ES6+ and then keep Gecko as well inside Firefox for

• adapt_throw 11y ago
  If the point is to make a more secure browser, allowing a webpage to opt-in to use the old, less secure engine instead is probably a non-starter. (In any case, I think the complexity is fundamental to many of the specs involved.)
• TazeTSchnitzel 11y ago
  HTML5 is no smaller than its predecessors. It's considerably larger.
• gsnedders 11y ago
  HTML5/CSS3/ES6 define how to process legacy content as well as current — the only actual branching for versions is quirks mode and that has relatively minor effects which aren't that much code to implement. Edge should, in principle, support everything, including legacy sites (at least as well as other browsers do today). Trident is only being kept around for sites that do extensive UA sniffing and rely on obscure behaviour — and pretty much only for the intranet.
• Manishearth 11y ago
  Gecko is not exactly separable from Firefox (unlike Blokc/Webkit and I'm guessing Trident/Spartan). The firefox UI depends heavily on things like XUL and XPCOM and whatnot which are nonstandard features in Gecko and would be a pain to support in Servo. I guess you could run two browser engines -- one for the UI, one for the content, but I'm not sure how well that would work.