Shadow DOM Style Scoping Note

Supported ShadowDOM style scope mechanisms, not assumed all styles/inheritance stopped at shadow boundary. Explicit supplied computed/layout context only; not a browser cascade/layout engine or cross-browser guarantee.

Description

Shadow-tree styling has boundaries and explicitly exposed entry points.

Shadow-tree styling has boundaries and explicitly exposed entry points.1

Host, slotted and part targeting serve different purposes rather than piercing every descendant. Use Shadow DOM Style Scoping Note to look up a supported term.

When to use Shadow DOM Style Scoping Note

Use Shadow DOM Style Scoping Note to look up a supported term. Choose the exact supported token from the table; preserve its punctuation and capitalization.

How to use Shadow DOM Style Scoping Note and understand its results

  1. Choose the exact supported token from the table; preserve its punctuation and capitalization.
  2. Enter Selector scope using the field table and validation rules below, then run the tool.
  3. Read Meaning and interpret units, signs, ordering and placeholders as explained below.
  4. If the tool reports an input error, correct that field and rerun. A successful false result, empty match list or unknown-evidence placeholder has the specific meaning described here; check the limitations before applying the result.
Input fieldMeaningValue typeRequirement
selectorScopeSelector scopestringRequired; constraints below

Enter one of the exact supported selectorScope tokens in the table below. The implementation performs a case-sensitive lookup and returns the stored meaning without interpreting a stylesheet, audio recording or performance. Unsupported tokens, added whitespace and alternate capitalization are input errors. The entries describe a bounded vocabulary rather than every valid value in the wider topic.

meaning = storedTable[exactSupportedToken]

Field order, units and branch conditions follow the implementation explanation above.

Exact supported tokenStored meaning
documentordinary document selectors do not pierce a shadow tree
shadowordinary shadow selectors apply within their shadow tree
hosthost pseudo-class targets the shadow host in shadow stylesheet context
slottedslotted pseudo-element targets assigned slotted elements, not arbitrary deeper descendants
partpart pseudo-element can target explicitly exposed shadow parts
Output fieldMeaningValue type
meaningStored explanation for the exact supported token.string
json
{
  "input": {
    "selectorScope": "slotted"
  },
  "output": {
    "meaning": "slotted pseudo-element targets assigned slotted elements, not arbitrary deeper descendants"
  }
}

Limitations and assumptions

Host, slotted and part targeting serve different purposes rather than piercing every descendant. Apply the exact scope and assumptions described above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are stated above; extremely large inputs or outputs can also be rejected. These errors differ from successful results such as false, no matches or unknown evidence.

Alternative or Complementary methods

Use z-index Stacking Context Boundary Check for a related task: A stacking context groups local paint-order comparisons within a larger hierarchy.

Use contain Strictness Levels Lookup for a related task: Containment separates selected effects on layout, painting, sizing and style.

References

  1. Shadow DOM Style Scoping Note — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies