Thanks for your interest in improving this project. Contributions here and upstream help make shadow DOM behavior more transparent and easier to reason about.
You can contribute directly to this dashboard or help move the platform forward more broadly.
Quick Paths
Templates are available in the repo for each designated contribution path to help guide you.
- Something is wrong / missing? Open an Issue (correction).
- Think a rating should change? Open an Issue (rating change proposal).
- Want us to track a new feature? Start a Discussion (feature proposal).
- Have a concrete fix? Open a Pull Request.
Direct Contributions
We welcome issues, pull requests, and discussions.
Updates & Corrections
If something looks incomplete, unclear, or incorrect:
- Open an issue to describe the problem
- Submit a pull request with corrections or additional context
You can also use issues or PRs to:
- Propose new or expanded Web Platform Tests (WPT) for tracked features
- Submit additional issue links or related resources
- Suggest adjustments to feature summaries
If you believe a feature’s support rating should change, use the rating change issue form so we can discuss the reasoning and evidence.
Suggesting a New Feature to Track
Use the feature proposal discussion form. The most helpful proposals include:
- The feature name
- A brief description of how it behaves in shadow DOM
- Any known expectation mismatches between light and shadow DOM
- Links to relevant WPT tests (if available)
- Relevant CSSWG issues and/or browser bugs
We prioritize features with architectural impact or known cross-context complexity.
External Contributions
This dashboard reflects the current state of behavior, but improving that behavior happens upstream.
You can help by:
- Sharing this resource with your team or community
- Filing or contributing to CSSWG and browser issues
- Adding implementation insight or real-world use cases to linked discussions
- Proposing new or expanded WPT coverage
Improving test coverage and clarifying specs benefits the entire ecosystem. Thanks for helping keep this information accurate and useful as the platform evolves!
Getting started
- Review the repo’s
CONTRIBUTING.mdfor workflow details - Use the templates (Issues / Discussions / PRs) to keep things consistent