-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/02/2015 08:21 PM, Manish Goregaokar wrote: > We've recently had two <https://github.com/servo/servo/pull/7845> > cases <https://github.com/servo/servo/issues/7720> where: > > - The spec suggests something which if implemented correctly, would > lead to inefficiencies - Major browsers do not follow that portion > of the spec and usually have a faster/cleaner implementation which > isn't spec-conformant. They usually don't match on how it's done, > either. - Spec bugs on the issue haven't really gotten anywhere > > We have three choices here, we can wait indefinitely until the spec > gets fixed, we can implement the spec as is (which require major > changes and affect perf or complexity), or we can hope that nobody > relies on this behaviour (given that it's not followed by major > browsers) and implement it as logically as possible, keeping in > line with other browsers (and leaving a bug open about the spec > issue). >
I'm not sure why you scoped this to inefficient spec algorithms. In any case where the specifications is wrong (in particular, where all browsers consistently disagree with the specification, and no browser vendor wants to match the specification in the (possibly distant) future), we should submit that feedback, write tests, and implement the interoperable behaviour. HTH Ms2ger -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJWOiiDAAoJEOXgvIL+s8n2lgQH/1Zns5Mdc8jtnyxrldC+Luh4 BTJJoLjvtfPQZp/NA7Q8E1Xy3pCRrguJTWQCZHSx0g1+vsH2/fclr0JsF3hRQ4bS ztE3Ww/mWJDQVk/eKTesYyKqExOxLT1bkUajeIov4SNBrke6kR7kAjJOzx2cAaD+ g8kf+rXo5a1HmQprsKRuWrpLdYsZxDHBXW+uGchyqB1TO5Wc5Pni1dfXvC5zDG+y UvtHpeLBz3MrCPhYoCFtLB/d7x6/jnP9+UsBBl9YY7DGW1TmtcXIlC1rexYSgzGU E//G0l9+D4p6YhOsAr6QhquZUXvkyusvH/gbhqJ9fhXrZMWfI9jxaq4syazoK3A= =A0uJ -----END PGP SIGNATURE----- _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
