Unicode non-character being treat as space on Firefox/Chrome
d at domenic.me
Thu May 25 15:19:34 UTC 2017
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 <es-discuss-bounces at mozilla.org> on behalf of Gareth Heyes <gareth.heyes at portswigger.net>
Sent: Thursday, May 25, 2017 10:52:52 AM
To: Mark S. Miller
Cc: es-discuss at mozilla.org
Subject: Re: Unicode non-character being treat as space on Firefox/Chrome
On 25 May 2017 at 14:04, Mark S. Miller <erights at google.com<mailto:erights at google.com>> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss