- From: Ilya Grigorik <notifications@github.com>
- Date: Mon, 30 Oct 2017 23:29:14 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 31 October 2017 06:29:41 UTC
@mnot ah, neat-o! I like that direction. I see some activity on the Chrome prototype @ https://bugs.chromium.org/p/chromium/issues/detail?id=751996, but it's not clear to me how the roadmap looks like from here and what hidden risks are yet to be discovered. For example, implications of blocking response processing while policy is fetched and applied ([design sketch](https://docs.google.com/document/d/e/2PACX-1vQpEp41ygL1sA6EL2roPEk8UK3hT-HEQD7Sr-W13e6DNetp49mQ_L6M57thFWyl-bIuMNGZOMwfHa5z/pub)). I'd like to suggest that we should pursue these efforts in parallel. We have lots of folks and use cases waiting to be unblocked via Accept-CH + Accept-CH-Lifetime, and if down the road we can enable alternative opt-in functionality via OP.. great! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/206#issuecomment-340672638
Received on Tuesday, 31 October 2017 06:29:41 UTC