Shared publicly  - 
An experimental Content Security Policy feature detection API just landed in today's Chrome Canary channel. Things have changed a bit from the initial proposal made back in May, and I think the current implementation is a good deal better than what I'd originally proposed.

The current working draft of the API's spec is available at, and comments are very welcome on the public-webappsec@ mailing list (

What do you think, +AngularJS? :)
Igor Minar's profile photoMike West's profile photo
Is there a 1.0 vs 1.1 spec diff?
+Igor Minar It doesn't exist in the 1.0 spec, so, yes. Slight difference. :)
I meant git-like diff of the text
Add a comment...