Unicode non-character being treat as space on Firefox/Chrome
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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss