WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED LATER
103390
CSP 1.1: Decide when to move some directives out from behind CSP_NEXT.
https://bugs.webkit.org/show_bug.cgi?id=103390
Summary
CSP 1.1: Decide when to move some directives out from behind CSP_NEXT.
Mike West
Reported
2012-11-27 04:08:20 PST
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
Comment 1
2012-11-27 04:08:49 PST
Er. Actually CCing Peter and Adam. :)
Mike West
Comment 2
2012-11-27 05:04:56 PST
(This bug, of course, assumes that the 1.1 spec goes to FPWD)
Adam Barth
Comment 3
2012-11-27 09:30:06 PST
That might make sense. I don't think we need to be in a big rush though.
Mike West
Comment 4
2012-11-27 10:03:07 PST
(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
Comment 5
2013-02-08 04:52:49 PST
I was crazy for filing this. Seriously, crazy early. RESOLVED LATER.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug