RE: [websockets] Reintroducing onerror

On Tuesday, June 07, 2011 10:36 AM, Ian Hickson wrote:
> On Tue, 7 Jun 2011, Adrian Bateman wrote:
> > We have removed onerror from our implementation since the previous 
> > change and it's frustrating trying track against the spec with 
> > unexpected updates.
> That's the cost of being on the bleeding edge. It's very likely that it 
> will change again. Until we have implementation and authoring experience, 
> we will almost certainly continue to update the specification to address 
> new problems and use cases. If you want to implement things that don't 
> change, then wait til someone else has implemented it and shipped it. 
> Being on the bleeding edge means you are providing the feedback that 
> affects the specification's development.

I'm just asking for a little transparency here: as far as I can see there
were no bugs filed or public e-mail discussion on this nor was there any
explanation in the check-in to change the spec. We understand that things
change but we're hoping that we're getting close to Last Call and we'd
like an opportunity to participate in the discussion before things show
up unexpectedly at this point.



Received on Tuesday, 7 June 2011 17:46:31 UTC