[Webkit-unassigned] [Bug 118553] New: Hash navigation doesn't affect history when the page is retrieved from appcache

[bugzilla-daemon at webkit.org]

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

           Summary: Hash navigation doesn't affect history when the page
                    is retrieved from appcache
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: History
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: noam at webkit.org
                CC: andersca at apple.com, beidson at apple.com,
                    zherczeg at webkit.org, luiz at webkit.org


Created an attachment (id=206437)
 --> (https://bugs.webkit.org/attachment.cgi?id=206437&action=review)
Test case

This was reproduced on trunk and on shipping Safari, and is probably an old bug though search through the bug database didn't come up with anything concrete.
When performing hash navigation on the attached page, the hash changes appear in history if the page was retrieved from the server, but not if it's retrieved from the cache.

This is most likely related to SubstituteData, which is used both for cached resources and for errors.
Specifically HistoryController::updateBackForwardListClippedAtTarget() calls urlForHistory, which returns an invalid URL if the document load has SubstituteData.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.