Bug 103390
| Summary: | CSP 1.1: Decide when to move some directives out from behind CSP_NEXT. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Mike West <mkwst> |
| Component: | WebCore Misc. | Assignee: | Mike West <mkwst> |
| Status: | RESOLVED LATER | ||
| Severity: | Normal | CC: | abarth, peter |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 85558 | ||
Mike West
Some pieces of CSP 1.1 seem "stable" enough to move out from behind the CSP_NEXT flag (though they should remain prefixed).
I'd like to deflag `form-action`, `plugin-types`, and `script-nonce`. The DOM API seems like it needs enough work that it might not make sense to expose it to the stable channel as-is. Would prefixing be enough, or is is too early? I'm still trying to get a feel for how baked things need to be before we expose them to users, so I'd appreciate your input Adam (and Peter, who sparked this bug in the first place).
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Mike West
Er. Actually CCing Peter and Adam. :)
Mike West
(This bug, of course, assumes that the 1.1 spec goes to FPWD)
Adam Barth
That might make sense. I don't think we need to be in a big rush though.
Mike West
(In reply to comment #3)
> That might make sense. I don't think we need to be in a big rush though.
You're right. There's no hard milestone I think we need to hit, so there's no pressure to get these in front of folks. But if they're non-controversial, I'd like to start getting feedback (and bug reports!) from a broader community sooner rather than later.
Mike West
I was crazy for filing this. Seriously, crazy early. RESOLVED LATER.