Re: [xhr] statusText is underdefined

Is this really a problem? HTTP defines the form and encoding of the status
text, and WebIDL/ES defines the form and encoding of DOMString. Adding an
explicit conversion definition seems redundant and overspecified. I would
argue the same for all other cases in the spec where it calls out an
explicit (and unnecessary) conversion.

On Tue, Mar 27, 2012 at 3:23 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> The spec says:
>
>  Return the HTTP status text.
>
> But the HTTP status text is a sequence of bytes, while the return value
> for statusText is a DOMString.  The conversion from one to the other needs
> to be defined.
>
> -Boris
>
>