Javascript escape()/unescape() NO LONGER suitable for URI manipulation

[Jungshik Shin]

This is to announce that escape()/unescape() was changed
recently to make them compliant to ECMA 262 (ECMAscript edition 3).
It's fixed in bug 44272(http://bugzilla.mozilla.org/show_bug.cgi?id=44272).
As a result[2], escape() and unescape() MUST NOT be used for URI
manipulation
any more. For URI tweaking, you have to use encodeURI(),
encodeURIComponent(),
decodeURIComponent(), and decodeURI(), instead.

In bug 225695 (http://bugzilla.mozilla.org/show_bug.cgi?id=225695), I've
been working on a tree-wide sweep to replace escape()/unescape() for the
URI manipulation with en/decodeURI(Component). I'm making this announcement
to make sure that no one checks in new patches that use escape()/unescape()
the old-fashioned way (non-standard way).

For details, refer to two bugs mentioned above and the following documents:

ECMA 262 :
http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf

MSDN article :

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/js56jsmthencodeuricomponent.asp

Jungshik