[webkit-changes] [WebKit/WebKit] 79c78c: [Navigation] Entry state can be lost during traver...

[Chris Dumez]

  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 79c78cf13ab46767853da09b1c8d0f7a5efa9981
      https://github.com/WebKit/WebKit/commit/79c78cf13ab46767853da09b1c8d0f7a5efa9981
  Author: Chris Dumez <cdumez at apple.com>
  Date:   2024-12-05 (Thu, 05 Dec 2024)

  Changed paths:
    M LayoutTests/imported/w3c/web-platform-tests/navigation-api/state/same-document-away-and-back-location-api-expected.txt
    M LayoutTests/imported/w3c/web-platform-tests/navigation-api/updateCurrentEntry-method/same-document-away-and-back-location-api-expected.txt
    M Source/WebCore/loader/FrameLoader.cpp
    M Source/WebCore/page/Navigation.cpp
    M Source/WebCore/page/Navigation.h
    M Source/WebCore/page/NavigationHistoryEntry.h

  Log Message:
  -----------
  [Navigation] Entry state can be lost during traversals
https://bugs.webkit.org/show_bug.cgi?id=282627
rdar://139735948

Reviewed by Rob Buis.

As per [1], fragment navigations should maintain the previous NavigationEntry's
state object. This PR implements this behavior to make the corresponding WPT
tests pass.

[1] https://html.spec.whatwg.org/#scroll-to-fragid

* LayoutTests/imported/w3c/web-platform-tests/navigation-api/state/same-document-away-and-back-location-api-expected.txt:
* LayoutTests/imported/w3c/web-platform-tests/navigation-api/updateCurrentEntry-method/same-document-away-and-back-location-api-expected.txt:
* Source/WebCore/loader/FrameLoader.cpp:
(WebCore::FrameLoader::loadInSameDocument):
* Source/WebCore/page/Navigation.cpp:
(WebCore::Navigation::updateForNavigation):
* Source/WebCore/page/Navigation.h:
* Source/WebCore/page/NavigationHistoryEntry.h:

Canonical link: https://commits.webkit.org/287401@main



To unsubscribe from these emails, change your notification settings at https://github.com/WebKit/WebKit/settings/notifications