mdn / mdn/browser-compat-data

api.ShadowRoot.slotAssignment - `named` value not supported in Chromium 86

Open Beginner friendly
#30,182 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

data:api needs collector test
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Missing compatibility data

What information was incorrect, unhelpful, or incomplete?

In Chromium < 102 the default value of ShadowRoot.slotAssignment is "auto".

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Browser)

What did you expect to see?

Should add an entry like ShadowRoot.slotAssignment defaults to "named".

Did you test this? If so, how?

document.createElement('div').attachShadow({mode: 'open', slotAssignment: 'named'}) throws in Chromium 91.0.4464.0 and not in 92.0.4510.0.

document.createElement('div').attachShadow({mode: 'open'}).slotAssignment and document.createElement('div').attachShadow({mode: 'open', slotAssignment: 'named'}).slotAssignment are "auto" in Chromium 101.0.4949.0 and are "named" in 102.0.4983.0.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/ShadowRoot/slotAssignment

MDN metadata
MDN page report details
  • Query: api.ShadowRoot.slotAssignment
  • Report started: 2026-08-06T14:22:17.019Z

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the ShadowRoot.slotAssignment entry associated with the issue's MDN URL and compare it with the reported Chromium 86–101 and 102 behavior. Update the compatibility data so the default and named-value support reflect those observations, then verify the resulting entry against the issue's documented tests.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.