- From: <bugzilla@jessica.w3.org>
- Date: Sat, 09 Aug 2014 01:01:54 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25866
--- Comment #4 from David Dorwin <ddorwin@google.com> ---
Summary: I'm leaning towards "encrypted" because anything longer is either
inaccurate or too wordy.
Background:
* The event really means that the UA has encountered container data that
indicates that media data blocks {are possibly | are potentially | may be}
encrypted. The event type happens to provide that container data.
* Looking at other APIs, most event names appear to be one of the following:
- actions (in various tenses)
- noun-then-verb
"encryptedmedia" does not reflect the meaning or match the existing patterns.
If anything, "mediaencrypted" would be more consistent, though this would imply
that media was just encrypted.
"encryptedmediaencountered" would be better, but implies the UA has actually
encountered encrypted media, which is not necessarily true - the UA just
encountered a header.
The following are probably more accurate, though not very appealing:
* potentiallyencryptedmedia[data][encountered]
* encryptionheader[encountered]
* encryptiondata[encountered]
* initdataencountered
Lacking a good accurate and consistent name, "encrypted" seems the least
misleading.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 9 August 2014 01:01:56 UTC