#30746: Add Feature-Policy header support
-----------------------------+-------------------------------------
Reporter: Nick Pope | Owner: Nick Pope
Type: New feature | Status: assigned
Component: Utilities | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+-------------------------------------
Comment (by Adam (Chainz) Johnson):
I'm -1 on adding Feature-Policy to Django... right now. It's far too
experimental and evolving much faster than Django's release cycle.
I created django-feature-policy to support it in October last year. Since
then I've done two "breaking changes" releases to update to the supported
set of headers: https://github.com/adamchainz/django-feature-
policy/blob/master/HISTORY.rst
It's still an actively developed w3c spec: https://github.com/w3c
/webappsec-feature-policy/commits/master . Also on the MDN page the
support grid shows that most support, even in Chrome, remains behind
feature flags: https://developer.mozilla.org/en-
US/docs/Web/HTTP/Feature_Policy#Browser_compatibility
I think it'll be settled in a year or so and then it'll be worth adding to
Django core.
--
Ticket URL: <https://code.djangoproject.com/ticket/30746#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.56dd018074f450045879a9651308924f%40djangoproject.com.
