> Considering that Servo is an embeddable engine, why not keep the scope of Servo focused in building a standards-compliant engine? So far, we are (as far as

> Considering that Servo is an embeddable engine, why not keep the scope of Servo focused in building a standards-compliant engine? So far, we are (as far as I know)! We try very hard to avoid nonstandard behavior, and if we can't avoid it, try to push for its inclusion in the standard. Given that there are no users that rely on Servo, we can even wait for the standard to be changed before implementing it. We often try to implement the standard to the word, with code that closely matches up to the standard. This has helped find tons of bugs in the standard (or in the tests). Nonstandard behavior in components shared with Gecko are off in Servo mode. But if Servo is to be a product we probably will have to change our stance here eventually.