3 ms·
Well, from my point of view it's less work to implement it than it is to argue removal from Gecko (which could happen, but it would take a while). Stylo must ha
by Manishearth 9y ago
Well, from my point of view it's less work to implement it than it is to argue removal from Gecko (which could happen, but it would take a while). Stylo must have Gecko parity, whether it's by adding more features to stylo or unshipping features from Gecko. We've done the latter in some cases for nonstandard stuff folks no longer use.
I don't really know what the future of MathML is. Some folks seem to still use it, though less often on web pages.
- leeoniya 9y agoThanks. Also, does Servo incur any overhead from Stylo having to implement legacy or Gecko-parity features (eg -moz prefixes, etc)? Or does Servo not use Stylo directly? Same question for other Quantum components.
- Manishearth 9y agoStylo is the project name for taking Servo's CSS system and hooking it up to Gecko. We conditionally compile out unsupported stuff. There is some complexity in shared code introduced but very little of it is anything but a complication of the abstractions (not an actual behavior-level change which can have a perf impact). So for example the weird cascading behavior exists when you compile pure servo (because that's a core functionality of font-size, which servo does implement), but servo doesn't have to deal with the mathml stuff or text-zoom. Servo has some no-op code for text-zoom that lets shared code be written cleaner, but it compiles out.
- SidiousL 9y agoPlease, please, please, don't take MathML away from us. Even though we are few in number, we want to be able to put mathematics on the Web. I'm sad Chrome and IE chose not to implement support for MathML.