We should probably move this to a GitHub issue then, so ES can have clarity on it.
If it helps, I am pretty sure (although I should double-check) that HTML treats such noncharacters as conformance errors (i.e. external tools like validators will warn you about them), but does not let them impact the processing model; they are passed through as-is. ________________________________ From: es-discuss <[email protected]> on behalf of Gareth Heyes <[email protected]> Sent: Thursday, May 25, 2017 10:52:52 AM To: Mark S. Miller Cc: [email protected] Subject: Re: Unicode non-character being treat as space on Firefox/Chrome On 25 May 2017 at 14:04, Mark S. Miller <[email protected]<mailto:[email protected]>> wrote: What is the relevant EcmaScript standards text that would delegate to this? Even if Unicode implies an undefined case, EcmaScript should not. If EcmaScript behavior for such cases is undefined, we should define it. Looking at the spec. it seems undefined. 0xfffe isn't defined as a whitespace character. This is probably why we have different behaviour in different browsers.
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
