On Jan 11, 2014, at 10:07 AM, Anne van Kesteren wrote:

> On Sat, Jan 11, 2014 at 5:57 PM, Brendan Eich <brendan at mozilla.com> wrote:
>> Allen Wirfs-Brock wrote:
>>> Another nit:  the definition of "ASCII whitespace" is different from the
>>> definition of whitespace used by String.prototype.trim [1].  That means that
>>> an implementation of this spec. that was implemented using JS couldn't use
>>> S.p.trim to process labels as described in the spec.
>>> 
>>> [1]:
>>> http://people.mozilla.org/~jorendorff/es6-draft.html#sec-string.prototype.trim
>>> <http://people.mozilla.org/%7Ejorendorff/es6-draft.html#sec-string.prototype.trim>
>> 
>> This seems more than a nit!
> 
> You cannot use that method for CSS, HTML, HTTP, etc. either. For this
> API we could have a different definition of whitespace I suppose, but
> e.g. for <meta charset=...> I doubt we could do that without risking
> breakage (or at the HTML parser level, say).

I'm only talking about this specification and what it takes to decouple it from web platform dependencies.  In this case, ASCII whitespace seems to only be used in processing the label parameter passed to the TextDecoder and TextEncoder constructors.  So, it isn't clear how CSS or anything else is relevant to that. 

Allen

I'm only talking about this specification and what it takes to decouple it from web platform dependencies.  In this case, ASCII whitespace seems to only be used in processing the label parameter passed to the TextDecoder and TextEncoder constructors.  So, it isn't clear how CSS or anything else is relevant to that.