Re: [dev-servo] Handling cases where the spec is inefficient and not followed by anyone

2015-11-04 Thread Manish Goregaokar
Oh, yeah, in that case we should just mimic the other browsers and file bugs. -Manish Goregaokar ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

Re: [dev-servo] Handling cases where the spec is inefficient and not followed by anyone

2015-11-04 Thread Boris Zbarsky
On 11/4/15 12:09 PM, Manish Goregaokar wrote: I'd prefer to avoid diverging from the spec wherever possible -- even if other browsers disagree (with the spec and with each other) I think Ms2ger was talking about cases in which the spec disagrees with all browsers, who agree with each other.

Re: [dev-servo] Handling cases where the spec is inefficient and not followed by anyone

2015-11-04 Thread Manish Goregaokar
On Wed, Nov 4, 2015 at 9:17 PM, Ms2ger wrote: > I'm not sure why you scoped this to inefficient spec algorithms Because inefficient or complexity-inducing specs cause problems, the rest, less so. If the spec isn't consistently implemented across the board, but implementing the spec is low-effo

Re: [dev-servo] Handling cases where the spec is inefficient and not followed by anyone

2015-11-04 Thread Ms2ger
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/02/2015 08:21 PM, Manish Goregaokar wrote: > We've recently had two > cases where: > > - The spec suggests something which if implemented correctly, would >

Re: [dev-servo] Handling cases where the spec is inefficient and not followed by anyone

2015-11-03 Thread Boris Zbarsky
On 11/3/15 4:52 AM, David Bruant wrote: @Manish: additionally, perhaps leave a comment in the open spec bug Oh, yes. Any time the spec does not match reality or sanity, do let the spec author know. -Boris ___ dev-servo mailing list dev-servo@lis

Re: [dev-servo] Handling cases where the spec is inefficient and not followed by anyone

2015-11-03 Thread David Bruant
Le 02/11/2015 21:00, Boris Zbarsky a écrit : On 11/2/15 2:21 PM, Manish Goregaokar wrote: 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 rel

Re: [dev-servo] Handling cases where the spec is inefficient and not followed by anyone

2015-11-02 Thread Boris Zbarsky
On 11/2/15 2:21 PM, Manish Goregaokar wrote: 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 follo

[dev-servo] Handling cases where the spec is inefficient and not followed by anyone

2015-11-02 Thread Manish Goregaokar
We've recently had two cases 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