[Bug 27271] Normatively require https for all ancestor origins when requiring https at all

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27271

Mike West <mkwst@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mkwst@google.com

--- Comment #3 from Mike West <mkwst@google.com> ---
(In reply to Glenn Adams from comment #1)
> I oppose adoption of this proposal due since it would dictate policy for the
> use of EME, which IMO is the prerogative of users of EME, and not the EME
> specification.

The language Henri proposes is clearly conditional ("When you want to do X, you
must do Y."), and justified ("Note: If you don't do Y, doing X doesn't really
do X."). What are we doing when specifying a thing if not noting the
guidelines, expectations, and consequences for its use?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 7 November 2014 19:24:07 UTC