- From: Adam Barth <ietf@adambarth.com>
- Date: Sun, 19 Jun 2011 14:47:52 -0700
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: public-iri@w3.org
On Sun, Jun 19, 2011 at 7:15 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 6/19/11 10:14 AM, Boris Zbarsky wrote: >> >> On 6/18/11 8:06 PM, Bjoern Hoehrmann wrote: >>> >>> A quick one is checking whether there is >>> a special rule for something resembling the "javascript" scheme for the >>> "#" character. >> >> For what it's worth, Gecko's behavior on this particular issue may be >> changing as of Firefox 6 to treat '#' in a javascript: URI as the start >> of a fragment identifier, assuming we don't find compat issues with it. > > Though to be clear, the script text that is executed will continue to > include everything after the 'javascript:', including the fragment > identifier. So the difference may not be detectable. Does that mean if a new document arises from evaluating the JavaScript URL that you'll scroll the page to the indicated fragment? In the resulting document, will location.hash contain the part after the # ? What will assigning to location.hash do (e.g., re-evaluating the JavaScript URL or just scroll the page)? Adam
Received on Sunday, 19 June 2011 21:48:51 UTC