Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve Frame Visit caching issue #644

Merged
merged 1 commit into from
Jul 28, 2022
Merged

Conversation

seanpdoyle
Copy link
Contributor

Closes #643

First, rename the FrameRendererDelegate.frameExtracted callback method
to willRenderFrame, then pass along both the current frame and the
new frame as arguments.

Next, in the FrameController.willRenderFrame callback, assign the
previousFrameElement property (used elsewhere in the
visitCachedSnapshot callback) to contain the contents of the current
frame, instead of the new frame.

Closes hotwired#643

First, rename the `FrameRendererDelegate.frameExtracted` callback method
to `willRenderFrame`, then pass along both the _current_ frame and the
_new_ frame as arguments.

Next, in the `FrameController.willRenderFrame` callback, assign the
`previousFrameElement` property (used elsewhere in the
`visitCachedSnapshot` callback) to contain the contents of the _current_
frame, instead of the _new_ frame.
@dhh dhh merged commit 1563ebb into hotwired:main Jul 28, 2022
@seanpdoyle seanpdoyle deleted the fix-issue-643 branch July 28, 2022 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

[main branch] Cache is incorrect when navigating using promoted frames
3 participants