[CSS] Enable CSS namespace exposure in workers and worklets on Nightly

Open
#46,467 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
css
Domain
documentation

Research direction

Start with the linked Gecko bug 2079583 to identify which CSS namespace features are exposed in workers and worklets on Nightly. Review the relevant MDN pages, browser compatibility data, and Firefox release notes or experimental features page; update the documentation and BCD as needed, then check whether related content issues can be resolved. MDN's core writers are handling this work, so consult the contributor board for issues accepting pull requests.

Written by the indexing model from the issue text.

Description

Content:CSS Firefox 161

[!IMPORTANT]
This issue will be worked on by MDN's core team of writers. If you want to contribute, please see the contributor board for issues where we're accepting pull requests.

Acceptance criteria

  • The listed features are documented sufficiently on MDN
  • BCD is updated
  • Interactive example and data repos are updated if appropriate
  • The content has been reviewed as needed
For folks helping with Firefox related documentation

[!NOTE]
Release notes are now generated at the beginning of the cycle, so a review is all that should be needed for the task. Obviously if there is a gap, fill it.

  • Set bugs to dev-doc-complete
  • Review/add entry to Firefox release notes for enabled/preview features
  • Add/remove entry to Firefox experimental features page for preference/released features

Related Gecko bugs

  • Bug 2079583 — Enable CSS namespace exposure in workers and worklets on Nightly

Other

  • Check content open issues to see if any pertain to the subject matter. If there are any that can be closed because of the work, do so. If there are any that can be fixed relatively quickly because of the knowledge from completing this issue and you have time, feel free to go ahead and fix them.
Dominant language
Markdown
Stars
11.1k
Forks
23.3k
Avg merge
2d 12h
Merged PRs (30d)
187

Getting set up

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.

More from mdn/content

All issues in mdn/content

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.