#292: Feature Policy JS introspection API
Discussions
2019-06-26
Dave: [reads tea-leaves] I think this needs a breakout. 304/303/389
... cors-like bit...
Sangwhan: happy to do a breakout.
Dave: we can figure it out time-zone wise.
Sangwhan: this could change how you substrate protocols - layered protocols - http3 runs on top of quic - quic runs on UDP. Also we have DNS over http - a protocol that has been pulled up. CHanges the dynamics...
Hadley: so you would say dns over http is a substrate of http?
Sangwhan: yes.
Peter: Breakout on this? Milestone on breakout session - a generic one...
Hadley: label?
Dan: feels more like a label
Peter: ok but then set a milestone when you are done with the breakout...
Alice: there is also a new TAG review to web transfer API - which is 389 so you may want to pull that into the breakout as well.
Peter: should we close 303?
Alice & Sangwhan: no
Alice: 2 separate things.
Dave: possible it's 304 and 389 but we can sort it out in the breakout...
[set for breakouts
OpenedJul 4, 2018
Hello TAG!
I'm requesting a TAG review of:
feature-policy-frame-policy-*
,feature-policy-header-policy-*
, andfeature-policy-nested-header-policy-*
tests. Once available, this API can also be used to test many other policy-controlled features, as well.Further details (optional):
You should also know that...
[please tell us anything you think is relevant to this review]
We'd prefer the TAG provide feedback as (please select one):
Please preview the issue and check that the links work before submitting
For background, some decent explainers:
https://github.com/w3c/ServiceWorker/blob/master/explainer.md https://github.com/zkoch/paymentrequest/blob/gh-pages/docs/explainer.md https://github.com/WICG/IntersectionObserver/blob/gh-pages/explainer.md (although this one includes IDL, which an explainer should not)