Re: Advice about unprefixing Content-Security-Policy in WebKit

I still think the solution to this issue is adding a mandatory v=1.1
parameter to CSP 1.1.  It will be unambiguous (the lack of it will
identify 1.0), and it'll allow backwards-incompatible changes to 1.1
and future revisions.  And it's not terribly long.

-tom

Received on Wednesday, 29 August 2012 00:21:45 UTC