New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 600513 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Disable Content-Security-Policy-Report-Only in meta elements

Project Member Reported by est...@chromium.org, Apr 4 2016

Issue description

Report-Only mode isn't allowed in <meta> tags per CSP 1.1, but we only enforce that when experimental CSP features are enabled.

There used to be a UseCounter for report-only in meta, but it got dropped (not clear whether intentionally or unintentionally) in https://chromium.googlesource.com/chromium/src/+/e9932e628fc3055c1f7c0980819d3601adfded24

Presumably we should do one of the following things:
- Add the use counter back in to decide whether we can take this out of experimental mode and remove support for real.
- Dig up institutional memory that remembers that the numbers were low enough back in 2014 that we can just remove support for report-only in meta elements.
- Decide that we can't remove support and remove this code path all together.
 
Cc: mkwst@chromium.org
+mkwst, what do you think?

Comment 2 by mkwst@chromium.org, Apr 5 2016

I think we can simply remove it. It's against spec, Firefox doesn't support it, and Edge doesn't support it. WebKit probably does, but we should align with the spec.
Sounds good, thanks. I'll do this once I finish removing support for the invalid directives in meta elements.
Status: Started (was: Assigned)
Labels: M-51
Status: Fixed (was: Started)

Sign in to add a comment