-
-
plehegar committed
Mar 14, 2017 -
-
Clean up uses of "i.e." and "e.g." (#362)
Also remove a gender-specific pronoun.
-
Do not reference JavaScript (#361)
Specs are not technically specific to JavaScript.
-
Fix #358: Clarify text about closing the CDM key session when a Media…
…KeySession becomes inaccessible (#359) Also use "key session" in several places to be consistent and differentiate.
-
Fixed #353: REmoved list of at-risk features from SOTD (#357)
Fixed #353: Removed list of at-risk features from SOTD
-
Fix #353: Remove persistent-usage-record from the V1 spec (#354)
Remove persistent-usage-record from the V1 spec * Updated to address feedback
-
Fix order consistency of one more pair of records reference.
This was missed in 97bec5e.
-
Fix #336: Allow implementations to finish rendering frames before fir…
…ing waitingforkey (#349)
-
Use consistent terminology for records of license destruction and key…
… usage (#350) Use the macros as much as possible to avoid inconsistent terminology. This also addresses a missing "of" and an instance where "proof" was used.
-
Fix #333: Explicitly handle potentially-encrypted media data that doe…
…s not contain Initialization Data (#342) Separates the relevant steps from the Initialization Data Encountered algorithm and specifies when to call them.
-
Fix #340: Make event preconditions consistent with HTML spec (#345)
Also changes the Wait for Key to queue the waitingforkey event after setting readyState. This is also more consistent with the HTML spec.
-
Reorder the items in the User Tracking Mitigations section. (#331)
Related items are now closer to each other.
-
Fix #329: Make MediaEncryptedEventInit required in the MediaEncrypted…
…Event constructor (#330) Also makes the init dictionary attributes required.
-
Be more explicit and concise in exceptions related to [Distinctive] P…
…ermanent Identifiers
-
Define and use Distinctive Value
ddorwin committedSep 9, 2016 -
Move identifier requirement from the associable definition
ddorwin committedSep 9, 2016 -
Move note that Distinctive Identifiers are not necessarily unique clo…
…ser to the relevant condition (#326)
-
Clarify the summary in the identifier requirements section (#325)
The markup was incorrect, and "They" was ambiguous. The new text is consistent with the referenced subsection.
-
Remove explanation of why domain is insufficient (#324)
The "above" reference is unclear but probably referred to the TLS section for the Security instance. While the "above" reference could be replaced, this statement is probably unnecessary since secure origins are required and origin is explicitly used in the requirement.
-
Fix #320: Clarify that consent is required unless all recommendations…
… for Distinctive Identifier clearing are implemented (#321) Replaces "support the recommendations" with "follow all the recommendations"
-
This fixes a variety of source markup style issues, mostly related to the location of opening and closing tags. Some of the tags were added in commit bf4650e to fix up unbalanced tags. This commit eliminates unneeded pairs and moves others to the correct line. Indentation depth is fixed in a few places.