trusted-types icon indicating copy to clipboard operation
trusted-types copied to clipboard

A browser API to prevent DOM-Based Cross Site Scripting in modern web applications.

Results 86 trusted-types issues
Sort by recently updated
recently updated
newest added

It should reuse the logic from #418.

A WPT test (or subtest) should be added to test the elementNs parameter of getPropertyType

Currently the algorithms oddly change empty string to HTML namespace. That prevents using the methods with elements which are in "" namespace (whether or not that is actual useful). But...

The current test suite duplicates some tests such as the one inside of `Element-outerHTML.html`, which is the top subtest within `block-string-assignment-to-Element-outerHTML.html` it would be good to squash these down so...

It seems to me that for trusted types to be really successful at what they are aiming to do, they need very large scale adoption and there's a bit here...

https://w3c.github.io/trusted-types/dist/spec/#cross-document-vectors mentions that. Examples of instances not addressable appreciated.

Classes of injection sinks are: 1. IDL attributes, e.g. `someScript.src = someSrc`. 2. JS functions, e.g. `eval(someString)`. 3. DOM APIs, e.g. `someScriptElement.setAttribute("src", someSrc)`. This is required in order to ensure...

https://w3c.github.io/trusted-types/dist/spec/#introduction mentions "over 60 different injection sinks". However, the spec contains: 12 occurrences of "HtmlString" 6 occurrences of "ScriptString" 12 occurrences of "ScriptUrlString" Which is below 60. https://w3c.github.io/trusted-types/dist/spec/#injection-sinks mentions `The...

While crawling [Trusted Types](https://w3c.github.io/trusted-types/dist/spec/), the following links to other specifications were detected as pointing to non-existing anchors: * [ ] https://w3c.github.io/DOM-Parsing/#widl-Element-innerHTML * [ ] https://w3c.github.io/DOM-Parsing/#widl-Element-outerHTML * [ ] https://w3c.github.io/DOM-Parsing/#html-fragment-parsing-algorithm *...

Consider the following scenario: ``` setTimeout(null, 1); ``` In a TT environment this would require `null` to be TrustedScript value. Say we define a default policy to handle such cases...