Bug 182726

Summary: Safari progress bar doesn't disappear after changing URL fragment in address bar
Product: WebKit Reporter: Tobi Reif <tobi>
Component: Page LoadingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED MOVED    
Severity: Normal CC: achristensen, ap, beidson, dbates, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari Technology Preview   
Hardware: Unspecified   
OS: macOS 10.13   
URL: https://tobireif.com/demos/grid/grid.html

Description Tobi Reif 2018-02-13 02:40:47 PST
Load https://tobireif.com/demos/grid/ in Safari.

The blue loading bar appears and disappears - all good.

In the URL bar change the last character (the digit 1) to "2", enter.

The blue loading bar appears - but doesn't disappear.
Comment 1 Alexey Proskuryakov 2018-02-13 15:53:50 PST
Can you please clarify steps to reproduce? The URL doesn't end with "1" after loading this webpage for me.
Comment 2 Tobi Reif 2018-02-14 01:56:28 PST
The page has since changed - sorry!

Please try the provided steps with this URL:

https://tobireif.com/demos/grid/grid.html
Comment 3 Radar WebKit Bug Importer 2018-02-14 12:49:32 PST
<rdar://problem/37544933>
Comment 4 Alexey Proskuryakov 2018-02-14 12:50:15 PST
I could reproduce using Safari 11.0.3.
Comment 5 Tobi Reif 2018-02-15 02:35:09 PST
Thanks for investigating!
Comment 6 Daniel Bates 2018-02-15 11:05:31 PST
This is a bug in Safari with regards to updating the progress bar for same document loads. And the fix will be tracked in <rdar://problem/37544933>. This bug is not specific to <https://tobireif.com/demos/grid/grid.html>. It occurs whenever a person explicitly changes only the fragment portion of the URL in the address bar. That is, it does not occur when clicking on a hyperlink that navigates to a fragment in the same document (regardless of whether the fragment corresponds to an actual anchor name). Disregarding the policy decision phase of the load, a same document load finishes the load immediately without providing same kinds of progress updates to the embedding client (e.g. Safari) as it would have if it was a navigation to a different document.
Comment 7 Daniel Bates 2018-02-15 11:22:50 PST
Actually, this bug is a duplicate of <rdar://problem/11569602>.