docs(browser-navigation): add a Scenarios section to the SPEC - #52
Open
ivanbanov wants to merge 1 commit into
Open
docs(browser-navigation): add a Scenarios section to the SPEC#52ivanbanov wants to merge 1 commit into
ivanbanov wants to merge 1 commit into
Conversation
26 compact traces of the guard's behavior — one layer, release and consumption, forward/claims/reload, stacked layers, timing edges — each replayable end to end in the module's own vocabulary (arm, release, Back, Forward). States outright two outcomes the prose only implied: an abandoned entry absorbs one Forward press, and any re-plant truncates every parked watch above it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
What
Adds a
## Scenariossection topackages/dom/utils/navigation/SPEC.md(between### Reloadand## API): 26 compact traces ofinterceptBackNavigation/watchSpentEntrybehavior, grouped into one layer · release and consumption · forward, claims, reload · stacked layers · timing edges. Ships with the package (SPEC.mdis infiles), so a patch changeset rides along.Why
The behavior contract was complete but stated one mechanism per prose bullet — nothing let a reader replay a concrete flow end to end. The scenarios are replayable episodes in the module's own vocabulary (
arm,release,Back,Forward); the preamble definesreleaseas a close the module didn't cause (external, imperative, or similar), keeping caller vocabulary like Escape out of this spec — that mapping belongs to the layer that owns the key.Two outcomes the prose left implicit are now stated outright:
🤖 Generated with Claude Code