Update content-security-policy.json #4811
Conversation
Elchi3
added
the
data:http
|
Thanks for your PR! May I ask what your source for this data is? (Manual testing is a valid answer, but if you have any bugs or documentation to link back to, that would be a great help!) Oh and, welcome to BCD! |
| @@ -1610,7 +1610,7 @@ | |||
| "support": { | |||
| "chrome": [ | |||
| { | |||
| "version_added": null | |||
| "version_added": "77" | |||
There was a problem hiding this comment.
'null' is actually correct. This is currently in an origin trial, which are not tracked in BCD. The origin trial is currently scheduled to run through 78. Don't put 79 as the version. Origin trials have been extended beyond what's published. The decision on this feature won't be made for another month yet.
This applies to chorme, chrome_android, and webview_android.
There was a problem hiding this comment.
After a little browsing around, it appears that this is not just an origin trial, but also a runtime flag for experimental platform features -- see https://developers.google.com/web/updates/2019/02/trusted-types#get-started, which is linked on the origin trial registration page.
There was a problem hiding this comment.
That's local developer use specifically.
There was a problem hiding this comment.
I think what I'm getting at is: if it's a part of a flag available in chrome://flags, then shouldn't it be included in the browser compatibility data?
|
As I double checked, this api is still not supported ! |
trusted-types API is Enabled by default on Chrome 77