I believe that Unicode specification make it undefined behaviour. In effect, noncharacters can be thought of as application-internal private-use code points. Unlike the private-use characters discussed in Section 16.5, Private-Use Characters, which are assigned characters and which are intended for use in open interchange, subject to interpretation by private agreement, noncharacters are permanently reserved (unassigned) and have no interpretation whatsoever outside of their possible application-internal private uses
http://www.unicode.org/versions/Unicode6.0.0/ch16.pdf On Thu, May 25, 2017 at 12:33 PM, Gareth Heyes <[email protected] > wrote: > Hi all > > Not sure if this is a bug or not. Non-character is being treated as a > space even though it's not defined as one. Edge and Safari treat it as an > invalid character. > > ```javascript > �alert�(1)� > ``` > > In case the characters get mangled: > ```javascript > eval("alert"+String.fromCharCode(65534)+"(1)"); > ``` > > Cheers > Gareth > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
