Rather than locking CSP 1.1 behind a vendor prefix, we should support it on the unprefixed header iff the runtime flag is set.
This will have no effect on ports that currently disable the CSP_NEXT flag, and the 'X-WebKit-CSP' headers will continue to function just as they did before on all ports. The goal is simply to not accidentally lock early-adopters users into using a prefixed header for the 1.1 features they'd like to experiment with.
Created attachment 191113 [details]
Please wait for approval from email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org or email@example.com before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
Comment on attachment 191113 [details]
Clearing flags on attachment: 191113
Committed r144571: <http://trac.webkit.org/changeset/144571>
All reviewed patches have been landed. Closing bug.