Conversation
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
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.
Summary
Architecture
Active layout handlers are contributed during the adapter boot hook, before server calls and dehydration. Tombstoned dispatches are rejected by a pre-call guard, and the adapter later filters the initial browser listener effect during dehydration.
A dehydration-only overlay is insufficient because it changes browser subscriptions after SupportEvents has already authorized and resolved server dispatches. The ordered adapter preserves both sides without extending or replacing SupportEvents. If core events are disabled, the adapter skips itself.
Listener precedence remains component listeners, then On attributes, then the layout overlay. Tombstones are resolved before dynamic placeholders are expanded. Whole-map clearing and live post-mount reconciliation remain out of scope.
Verification