Sanitizer API
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js
Research direction
Start by reading the linked Sanitizer API WICG proposal, then compare its DOM-coupled design with the server-side use cases described here, including DOMPurify, jsdom, and happy-dom. Done means documenting whether WinterTC should provide input on string-to-string sanitization or pursue a limited DOM subset, with the scope and trade-offs made explicit.
Written by the indexing model from the issue text.
Description
The web Sanitizer API is still in flux. But maybe it’s worth considering whether it’s within scope of WinterTC early on.
- Server-side rendering (SSR) is becoming increasingly common.
- DOMPurify is widely deployed on Node and probably other JavaScript server runtimes.
Of course, the Sanitizer API is strongly coupled to DOM node objects; its current design extends Element and Document.
- But, while the spec is still in flux, it may be worth investigating whether WinterTC should provide input to the Sanitizer API WICG on any string-to-string transformations. Such a string-to-string sanitization API may still be useful in webpages and would definitely be useful in JavaScript server runtimes (or service workers in browsers).
- Alternatively, a very limited subset of the DOM could also be standardized by WinterTC, à la jsdom and happy-dom, and the Santizer API for servers would sit on that DOM subset. This would be a much bigger undertaking, but it could pay off.
- Dominant language
- Bikeshed
- Stars
- 308
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
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.
More from WinterTC55/proposal-minimum-common-api
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
WinterTC55/proposal-minimum-common-api#117 · 4 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
WinterTC55/proposal-minimum-common-api#107 · 4 reactions ·
-
2026 edition roadmap Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
WinterTC55/proposal-minimum-common-api#106 · 2 reactions ·
-
Serialization? Open
Difficulty 5/5 Over a week Newbie friendliness 18/100
WinterTC55/proposal-minimum-common-api#99 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in WinterTC55/proposal-minimum-common-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·