W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10625] New: Spec should cover stopping parsing on location.href = "foo"

From: <bugzilla@jessica.w3.org>
Date: Mon, 13 Sep 2010 19:21:03 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-10625-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10625

           Summary: Spec should cover stopping parsing on location.href =
                    "foo"
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: eric@webkit.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org


Spec should cover stopping parsing on location.href = "foo"

It seems that at least firefox and (historical) WebKit stop parsing whenever a
scheduled location change is made, such as through setting window.location.href
=.

This is not directly discussed in:
http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#the-location-interface

However
http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#navigate
does imply that parsing should stop if we get all the way to unloading the
document.   However existing browsers seem to stop parsing regardless of
whether the load is secure or successful, immediately after location.href is
set.

See https://bugs.webkit.org/show_bug.cgi?id=43328 for how we had to add this
quirk back into WebKit after moving to the HTML5 parser.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 13 September 2010 19:21:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:55 UTC