Reveal canon text when Way rows are opened - #27
Merged
Merged
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.
What changed
/way/heading link with a native<details>/<summary>disclosureunit.contentinline when the row is tappedRoot cause
The canon-derived tree rendered each row only as a navigation link. A click left the tree for a companion page, so the map itself never showed the text the row represented.
User impact
Every row now works as a one-tap reading surface, including without JavaScript. Opening a row does not change the
/way/URL. Deeper interpretation and provenance paths remain explicit rather than being collapsed into the disclosure.Validation
/way/automated accessibility check passedmain, zero behind, with exactly five intended fileshmmm
The local production aggregate gate could not complete because external canon/repository/textbook requests entered fallback twice; the validator correctly rejected fallback production data. The checked-in recovery canon is also stale against current Article drafts. GitHub CI is therefore the authoritative live-source gate for this PR.