Re: Should Decode accept U+FFFE or U+FFFF (and other Unicode non-characters)?

On Jul 14, 2011, at 10:38 PM, Jeff Walden wrote: Reraising this issue... To briefly repeat: Decode, called by decodeURI{,Component}, says to reject %ab%cd%ef sequences whose octets [do] not contain a valid UTF-8 encoding of a Unicode code point. It appears browsers interpret this

Re: Should Decode accept U+FFFE or U+FFFF (and other Unicode non-characters)?

Reraising this issue... To briefly repeat: Decode, called by decodeURI{,Component}, says to reject %ab%cd%ef sequences whose octets [do] not contain a valid UTF-8 encoding of a Unicode code point. It appears browsers interpret this requirement as: reject overlong UTF-8 sequences, and

Should Decode accept U+FFFE or U+FFFF (and other Unicode non-characters)?

I was looking at how SpiderMonkey decodes URI-encoded strings, specifically to update it to reject overlong UTF-8 sequences per ES5 (breaking change from ES3 that should generally be agreed to have been necessary, not to mention that existing implementations were loose and strict