[Webkit-unassigned] [Bug 179240] New: Navigation should "Cancel any preexisting but not yet mature attempt to navigate browsingContext"

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=179240

            Bug ID: 179240
           Summary: Navigation should "Cancel any preexisting but not yet
                    mature attempt to navigate browsingContext"
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: waldron.rick at gmail.com
                CC: annevk at annevk.nl, cdumez at apple.com

Step 6 of https://html.spec.whatwg.org/#navigating-across-documents :

  Cancel any preexisting but not yet mature attempt to navigate browsingContext, ...


While working on tests for spec cited above, I wrote the following test: https://github.com/rwaldron/web-platform-tests/blob/55441a8ca101f093ecde922c13770654e5ad5d39/html/browsers/browsing-the-web/navigating-across-documents/016-onclick-return-true-then-navigation.html

Using Safari Technology Preview, sometimes this test passes and sometimes it does not. Chrome, Firefox and Edge all consistently pass this test, but... there is something else to consider: there may be disagreement in implementations because the intended behavior appears to be vague and possibly underspecified. 

If all implementers agree that navigating iframe to the href should completely cancel the preexisting navigation for a nested browsing context, including removal of the task from the queue (created in https://html.spec.whatwg.org/#the-iframe-element:attr-iframe-src-5) and being taken out of delaying load events mode, then the normative specification can be updated with more explicit instructions. 

Alternatively, there is room for discussing whether or not that should be the behavior at all.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20171103/fa7ad148/attachment.html>