On Tuesday, June 07, 2011 10:36 AM, Ian Hickson wrote:
On Tue, 7 Jun 2011, Adrian Bateman wrote:
This check-in [1] reintroduces the onerror handler that was removed
previously [2]. Since, in general, WebSocket protocol errors are fatal
and result in onclose, what is the purpose of adding
On Tue, 7 Jun 2011, Adrian Bateman wrote:
This check-in [1] reintroduces the onerror handler that was removed
previously [2]. Since, in general, WebSocket protocol errors are fatal
and result in onclose, what is the purpose of adding this back?
Ian asked me to put it back so that authors
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
On Tue, 7 Jun 2011, Adrian Bateman wrote:
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
