Re: [xhr] Creating an ArrayBuffer can fail (#26)

Currently, Chrome crashes when it fails to allocate an ArrayBuffer as it wasn't specified to throw an exception in the spec at the time we decided how to handle the case.

Unless there'll be any confusion, returning null should be fine. What's the reliable way to distinguish alloc failure and other errors (network error)? Saw "load" being dispatched, but seeing null on response?

+1 to Boris regarding consistency.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/xhr/issues/26#issuecomment-144407891