The 1.0 draft of the Content Security Policy spec is just about to move to Last Call. Adam's suggested introducing an ENABLE flag in order to start working on the 1.1 spec while it's still in flux (https://dvcs.w3.org/hg/content-security-policy/raw-file/tip/csp-specification.dev.html).
Maybe ENABLE_CSP_NEXT or ENABLE_CSP_11 ? The DOT is kind of ugly. :)
The DOT was the clever bit! :( ENABLE_CSP_NEXT it is. I'll throw a patch at you shortly.
Do we need to send a note to webkit-dev?
Created attachment 148008 [details] I think this is all the relevant files...
(In reply to comment #3) > Do we need to send a note to webkit-dev? Sure.
Comment on attachment 148008 [details] I think this is all the relevant files... This looks right, but let's hold off landing it until you email webkit-dev.
(In reply to comment #6) > (From update of attachment 148008 [details]) > This looks right, but let's hold off landing it until you email webkit-dev. I've just sent an email, but I don't see any reason to rush. Let's give it a day or two and land the patch early next week if there's no objection.
Comment on attachment 148008 [details] I think this is all the relevant files... No one on webkit-dev complained.
Comment on attachment 148008 [details] I think this is all the relevant files... Clearing flags on attachment: 148008 Committed r120698: <http://trac.webkit.org/changeset/120698>
All reviewed patches have been landed. Closing bug.