Unicode non-character being treat as space on Firefox/Chrome

Gareth Heyes gareth.heyes at portswigger.net
Thu May 25 14:52:52 UTC 2017

On 25 May 2017 at 14:04, Mark S. Miller <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...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20170525/562d9cc5/attachment.html>

More information about the es-discuss mailing list