Repository navigation
docs: clarify language and direction inheritance in shadow DOM - #45537
Merged
Josh-Cena merged 2 commits intoSep 8, 2026
Merged
Conversation
Josh-Cena
requested review from
Josh-Cena
and removed request for
sideshowbarker
September 6, 2026 14:45
Contributor
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.
Description
Clarify the existing Attribute inheritance section in the Using shadow DOM guide. Explain parent-based inheritance across a shadow boundary and distinguish a slot's inheritance from that of its assigned light-DOM content.
Motivation
The current sentence implies that every slot inherits language and directionality directly from the shadow host, overlooking intervening shadow-tree ancestors. The replacement adds a short nested-slot example and retains qualifications and reference links for directionality exceptions, following the invitation to propose a focused update.
Additional details
The wording follows the HTML Standard's language rules and parent directionality algorithm, together with the DOM Standard's slot assignment rules.
Validation:
npm test: 12 passed, 0 failed.:lang(),:dir(), DOM parents and explicit attributes separately for nested slots, fallback content, assigned spans, explicit overrides, and directionality exceptions (bdiand telephone inputs).This is a one-file prose correction: no runtime, dependency or anchor changes. No cross-browser or assistive-technology testing is claimed.
AI assistance: Codex assisted with research, wording, validation and a separate exact-commit review.
Related issues and pull requests
Fixes #45249