Stream frames with declarative out-of-order directives - #11585
Draft
jacob-ebey wants to merge 1 commit into
Draft
Conversation
Non-blocking `<Frame>` streaming now uses the declarative out-of-order streaming directives instead of a runtime-driven template swap. Pending fallbacks are wrapped in `<?start name="ID">` / `<?end name="ID">` inside the existing `<!-- rmx:f:ID -->` markers, and resolved content streams as `<template for="ID">` (was `<template id="ID">`). Browsers that natively process the directives perform the DOM swap with no JavaScript. Other browsers use a small MutationObserver polyfill that `run()` installs automatically, which moves `<template for>` content into its region and removes the directives. In both cases the runtime no longer extracts templates itself; it hydrates the resolved region after the swap, while reloads and navigation continue to reconcile fetched-stream content through the template bus.
Contributor
Preview Build AvailableA preview build has been created for this PR. You can install it using: pnpm install "remix-run/remix#preview/pr-11585&path:packages/remix"This preview build will be updated automatically as you push new commits. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Non-blocking
<Frame>streaming now uses the declarative out-of-order streaming directives instead of a runtime-driven template swap. Pending fallbacks are wrapped in<?start name="ID">/<?end name="ID">insidethe existing
<!-- rmx:f:ID -->markers, and resolved content streams as<template for="ID">(was<template id="ID">).Browsers that natively process the directives perform the DOM swap with no JavaScript. Other browsers use a small MutationObserver polyfill that
run()installs automatically, which moves<template for>contentinto its region and removes the directives. In both cases the runtime no longer extracts templates itself; it hydrates the resolved region after the swap, while reloads and navigation continue to reconcile fetched-stream content through the template bus.