Missing Trusted Type support data for various sinks
Nobody has claimed this yet.
- 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?
Various APIs in BCD have an "accepts_TrustedXXX" entry which says which version of a browser accepts TrustedHTML, TrustedScript or TrustedScriptURL in a given sink. Only some of the applicable APIs have this data though.
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
I expected all TT sinks to have this data (or none of them).
Did you test this? If so, how?
N/A
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
No response
MDN metadata
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by searching the browser-compat-data repository for accepts_TrustedHTML, accepts_TrustedScript, and accepts_TrustedScriptURL entries, then identify Trusted Types sinks that lack corresponding data. Compare the existing entries with the applicable sink APIs and determine the complete coverage needed. Done means the relevant sinks have consistent compatibility data, with the repository's data validation passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100