- From: Hadley Beeman <notifications@github.com>
- Date: Tue, 10 Sep 2019 23:59:50 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 11 September 2019 07:00:12 UTC
Thanks, @estark37! Much more helpful intro now. I can see what you're trying to do and why! Note on 5.1: You might want to amend the text to say "...directive is not obsolete because it **also** allows developers to upgrade blockable content". As it is, we thought it sounds like this note was ignoring optionally-blockable content. We appreciate the risk you've outlined in section 6. It was on our minds too. It's the same risk as in `upgrade-insecure-requests`. This is a logical step on the path to the HTTPS-only web. Thanks for sharing it with us! -- 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/420#issuecomment-530249656
Received on Wednesday, 11 September 2019 07:00:12 UTC