From 3c3539fd972cc9d05bb7beb281faa928959a33a8 Mon Sep 17 00:00:00 2001
From: Anne van Kesteren
Date: Tue, 5 Jul 2016 13:29:53 +0200
Subject: [PATCH] Navigate: narrow down requirements for fragment handling
Only navigations for requests can cause fragment navigations to happen
synchronously.
---
source | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/source b/source
index bcdb1cc6c1e..4218ca08e29 100644
--- a/source
+++ b/source
@@ -81916,12 +81916,13 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O
If this is not a reload-triggered navigation,
- resource's URL equals
+ resource is a request, resource's
+ url equals
browsingContext's active document's URL with exclude fragments flag set, and
- resource's URL's fragment is
- non-null, then navigate to that fragment and abort these
- steps.
+ resource's url's fragment is non-null, then navigate to that fragment and abort these steps.
Cancel any preexisting but not yet mature
attempt to navigate browsingContext, including canceling any instances of the