Re: [xhr] Status 0 is missing a message (#35)

It's for representing the status-code and reason-phrase of the HTTP semantics. If we want to expose something not represented on the status line, we should extend the API surface for it. Embedding such info in the same attributes would be confusing, I think.

At least about CORS, there could be another reason why we don't expose details. It's basically better not to reveal any details about the cross-origin server when it doesn't understand CORS or reject cross-origin access.

For example, Chrome emits a console error explaining what happened. So, developers should be able to investigate it. Do you want to make it visible to script and gather error information (or show the error code to your customers so that they can report detailed info about the error) for debugging?

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