- From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
- Date: Tue, 22 May 2007 23:02:39 +0200
Problems with that: javascript URI scheme is not registered: <http://www.iana.org/assignments/uri-schemes.html> Support for this feature is undocumented, at least for Microsoft Internet Explorer: <http://msdn2.microsoft.com/en-us/library/Aa767736.aspx> It is not mentioned in HTML specification 4 either. And finally, in the specification 5, where that behavior is described for the first time: <http://www.whatwg.org/specs/web-apps/current-work/#refsJSURI>: When a browsing context is navigated to a javascript: URI, and the active document of that browsing context has a different origin than the URI, the dereference context must be an empty object. Which is the case with bookmarklets. Chris -----Original Message----- From: Maciej Stachowiak [mailto:mjs@apple.com] Sent: Tuesday, May 22, 2007 9:42 PM To: Kristof Zelechovski Cc: 'Ian Hickson'; judell at mv.com; whatwg at whatwg.org Subject: Re: [whatwg] password option for window.prompt? On May 22, 2007, at 12:16 PM, Kristof Zelechovski wrote: > Forgive my being nosy: which uses? > a href="javascript:." is valid but it replaces the current document > with a > document parsed from the textual representation of the value > returned from > the script. If the javascript: URI returns the undefined value (such as by using the void operator or by calling a method with no return type), then the target document is not replaced, but the side effect still occurs. Regards, Maciej
Received on Tuesday, 22 May 2007 14:02:39 UTC