Clipping of violation’s sample to the 40 first characters
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 662
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
See https://github.com/w3c/webappsec-csp/issues/704
The Trusted Types spec also mentions clipping to 40 first characters, and this can have similar ambiguity and implementation issues:
https://w3c.github.io/trusted-types/dist/spec/#should-block-sink-type-mismatch
https://w3c.github.io/trusted-types/dist/spec/#should-block-create-policy
(and in https://w3c.github.io/trusted-types/dist/spec/#privacy-considerations)
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 reading the linked CSP issue and the three Trusted Types specification sections on clipping. Determine what ambiguity the 40-character limit creates and what behavior or wording would resolve it. Done means the affected specification text has an agreed, unambiguous definition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100