19492 2012-10-12 03:05:31 +0000 Javascript URI Consumption and Composition 2013-11-21 12:59:17 +0000 1 1 1 Unclassified WHATWG URL unspecified PC Windows 3.1 RESOLVED DUPLICATE 13720 P2 normal Unsorted 1 shadow2531 annevk mike sideshowbarker+urlspec oldest_to_newest 76061 0 shadow2531 2012-10-12 03:05:31 +0000 Not sure if these will help with your Javascript URI research, but here it is anyway: Create Javascript URIs: <http://shadow2531.com/js/jsuri.html> <http://shadow2531.com/js/jsuri.js> (that jsuri.html uses) It does two things to the JS code you type: * Normalizes newlines to \r\n. * UTF-8-percent-encodes the code (using encodeURIComponent() on UTF-8 page). That's basically how you properly-encode a Javascript URI (for bookmarklet or other use). The percent-encoding is very important as browsers always percent-decode first and if you have %HH is URIs in JS code literal strings for example, they will be damaged when the browser percent-decodes the Javascript URI before it's executed. '#' isn't special in Javascript URIs. They're treated as just '#' by browsers (not necessarily the URI parser though, but the end result). Also, I haven't messed with these in a long time, but I once played around with creating a JS Javascript URI handling library. <http://shadow2531.com/js/javascript_uri_tools.js> <http://shadow2531.com/js/javascript_uri_tools.html> <http://shadow2531.com/js/js_uri_tools.js> getLiteralCodeStringFromURI() in js_uri_tools.js might be of interest from a consumption standpoint. (The URI isn't parsed with a URI parser to get the JS code for example as a URI parser isn't needed.) 80478 1 annevk 2012-12-21 14:23:49 +0000 http://wiki.whatwg.org/wiki/URL_schemes#javascript:_URLs 96636 2 annevk 2013-11-21 12:59:17 +0000 This is HTML's problem now. *** This bug has been marked as a duplicate of bug 13720 ***