[Webkit-unassigned] [Bug 282689] [Navigation] Fix remaining problems with traversals

[bugzilla-daemon at webkit.org]

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

--- Comment #6 from Chris Dumez <cdumez at apple.com> ---
(In reply to Chris Dumez from comment #5)
> navigation-methods/back-forward-multiple-frames.html has a top frame and an
> iframe.
> The test does this:
> 1. Navigate the top frame to "#top"
> 2. Navigate the iframe to "#iframe"
> 3. Call `navigation.back()` in the top frame
> 4. Expects both the top frame and the iframe to get navigated back (so that
> the fragment is removed from both) and a popstate event to get fired in both
> frames.
> 
> This works in Blink but in WebKit, only the top frame gets navigated and
> gets a popstate event. The iframe is still sitting on "#iframe" after
> calling `navigation.back()` in the top frame.

Looking at the `Navigation::back()` implementation, it does look like it doesn't quite match the specification and only navigates a single frame. In the spec, we're supposed to also navigate child frames if the navigation of the parent frame doesn't change document (i.e. just a fragment navigation).

-- 
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/20241209/cefe3874/attachment-0001.htm>