Wednesday, 29 June 2016
Saturday, 25 June 2016
Friday, 24 June 2016
- [media-source] Consider making MSE attachment asynchronous
- FW: Polyfill example
- RE: Additional EME tests
- [media-source] Normative reference to High Resolution Time is missing
Thursday, 23 June 2016
- [encrypted-media] Clear Key support for persistent-license sessions
- RE: Formal Objection to Candidate Recommendation
- [media-source] Calling endOfStream after duration truncation may yield greater duration
Wednesday, 22 June 2016
- [media-source] Need event to signal when decoder underflow has occurred
- MSE test suite status update
Tuesday, 21 June 2016
- Formal Objection to Candidate Recommendation
- Re: Creating effective RansomWare with EME
- Re: Creating effective RansomWare with EME
- Re: Creating effective RansomWare with EME
Monday, 20 June 2016
- [encrypted-media] A number of minor corrections.
- WG Decision: Publish EME Candidate Recommendation with "at risk" features
- WG Decision: Republish MSE Candidate Recommendation and modify "at risk" features
- Re: Creating effective RansomWare with EME
- Re: Creating effective RansomWare with EME
- Creating effective RansomWare with EME
Friday, 17 June 2016
- [media-source] Have appendBuffer and remove return promise.
- [media-source] The fetch step in HTML5.1's resource fetch algorithm no longer exists
Thursday, 16 June 2016
Monday, 13 June 2016
Saturday, 11 June 2016
Friday, 10 June 2016
- [encrypted-media] WedIDL: partial interface definition cannot specify inheritance
- [encrypted-media] Web IDL links in the EME WD point to the Web IDL ED
- MSE and EME timeline update
- CfC: Publish EME Candidate Recommendation with "at risk" features
- [encrypted-media] Explicitly state that distinctive and permanent identifiers may not be used without distinctiveIdentifier being "required"
- [encrypted-media] Revisit the steps where consent for distinctiveIdentifier is required
- [encrypted-media] Remove spec ISSUES related to #192, #207, #101 and #85; plus Issue #3 prior to CR.
- CfC: Republish MSE Candidate Recommendation and modify "at risk" features
- [encrypted-media] Implementations that support modes with and without distinctive identifiers SHOULD expose this to the user
- [encrypted-media] Add statement that all values exposed or inferable by the application must be per-origin
Thursday, 9 June 2016
- [encrypted-media] Privacy: Update User Tracking section, including to specifically address Permanent Identifiers
- [media-source] "effective script origin" is no longer a thing
Wednesday, 8 June 2016
- [encrypted-media] It may not be possible to return undefined from MediaKeyStatusMap.get()
- [media-source] TrackDefault.kinds attribute cannot have type sequence<DOMString>
- [encrypted-media] The Origin-Independent Individualization process would not generate a compliant Distinctive Identifier
Tuesday, 7 June 2016
- [media-source] Clarify/remove 'stalled' and 'progress' events for MediaSource
- [media-source] Add at-risk item "VideoPlaybackQuality" to MSE spec, per recent CfC
- [encrypted-media] Simplify logic for setting <var>use distinctive identifier</var> and <var>persistent state allowed</var>
Monday, 6 June 2016
- [encrypted-media] Normatively referenced recommendations in Allow Identifiers to Be Cleared algorithm have been moved
- [encrypted-media] Access of session's "record of key usage" in the MediaKeySession Destroyed and Session Closed algorithms is inconsistent
- W3C, EME and EFF: Frequently Asked Questions
Friday, 3 June 2016
- [encrypted-media] Complete review of security and privacy considerations sections
- [encrypted-media] Resolve question of support for insecure contexts
- [encrypted-media] Add more specific text about ensuring the desired privacy and cryptographic properties of identifiers
- EME: ISSUE boxes in the spec