issues
search
w3c
/
encrypted-media
Encrypted Media Extensions
https://w3c.github.io/encrypted-media/
Other
180
stars
80
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Do not reference JavaScript
#361
ddorwin
closed
7 years ago
0
Provide best practices for authors
#360
ddorwin
opened
7 years ago
2
Fix #358: Simplify wording about closing CDM session when MediaKeySession is destroyed
#359
ddorwin
closed
7 years ago
7
Remove requirement to close CDM session *before* destroying UA MediaKeySession state
#358
ddorwin
closed
7 years ago
2
Fixed #353: Removed list of at-risk features from SOTD
#357
jdsmith3000
closed
7 years ago
2
Fix#353: Remove at-risk list from the SOTD.
#356
jdsmith3000
closed
7 years ago
2
Move gh-pages branch to master
#355
ddorwin
closed
7 years ago
4
Fix #353: Remove persistent-usage-record from the V1 spec
#354
jdsmith3000
closed
7 years ago
14
V1: Remove the at-risk persistent-usage-record feature and the related MediaKeySession destroyed algorithm, and remove the at risk notation for setting the media element readyState based on key availabity in two algorithms
#353
jdsmith3000
closed
7 years ago
62
Consistently reference a target media element in algorithms
#352
ddorwin
closed
7 years ago
2
Reference session types and related data in a consistent order
#351
ddorwin
closed
7 years ago
0
Use consistent terminology for records of license destruction and key usage
#350
ddorwin
closed
7 years ago
0
Fix #336: Allow implementations to finish rendering frames before firing waitingforkey
#349
ddorwin
closed
7 years ago
8
Fix #347: Reset waiting for key and encrypted block queue when position changes
#348
ddorwin
closed
7 years ago
1
Internal waiting for key and encrypted block queue values must be cleared on seek
#347
ddorwin
closed
7 years ago
3
Fix #336: Allow implementations to finish rendering frames before firing waitingforkey
#346
ddorwin
closed
7 years ago
5
Fix #340: Make event preconditions consistent with HTML spec
#345
ddorwin
closed
7 years ago
2
Fix #335: Note that many implementations only support decryption with MSE
#344
ddorwin
closed
7 years ago
1
Fix #338: Allow Wait for Key algorithm to transition readyState to HAVE_CURRENT_DATA
#343
ddorwin
closed
7 years ago
1
Fix #333: Explicitly handle potentially-encrypted media data that does not contain Initialization Data
#342
ddorwin
closed
7 years ago
1
Fix #337: Allow remove for temporary sessions
#341
mwatson2
closed
7 years ago
0
Preconditions in HTMLMediaElement Event Summary may not be consistent with HTML spec
#340
ddorwin
closed
7 years ago
1
Should there be flexibility in when readyState is updated when waiting for a key?
#339
ddorwin
closed
7 years ago
5
Should Wait for Key set readyState to HAVE_CURRENT_DATA when playing?
#338
ddorwin
closed
7 years ago
8
Remove is-persistent-session-type-algorithm check from remove() algorithm
#337
ddorwin
closed
7 years ago
1
waitingforkey as spec'd could fire at different times in different browsers
#336
cpearce
closed
7 years ago
17
Spec should mention that EME is not expected to work outside of MSE
#335
cpearce
closed
7 years ago
2
Issue #329: Remove the prose for the removed messageType default value
#334
ddorwin
closed
7 years ago
2
Explicitly handle potentially-encrypted media data that does not contain Initialization Data
#333
ddorwin
closed
7 years ago
4
Fix #312: Require users be informed or provide consent when there are security concerns
#332
ddorwin
closed
7 years ago
1
Reorder the items in the User Tracking Mitigations section.
#331
ddorwin
closed
7 years ago
2
Fix #329: Make MediaEncryptedEventInit required in the MediaEncryptedEvent constructor
#330
ddorwin
closed
7 years ago
5
MediaKeyMessageEvent's message needs to be nullable or required in init dict
#329
foolip
closed
7 years ago
15
Fix #242: All values exposed to the application must be per-origin and clearable
#328
ddorwin
closed
8 years ago
2
Several small commits related to value and identifier definitions
#327
ddorwin
closed
8 years ago
2
Move note that Distinctive Identifiers are not necessarily unique closer to the relevant condition
#326
ddorwin
closed
8 years ago
1
Clarify the summary in the identifier requirements section
#325
ddorwin
closed
8 years ago
2
Remove explanation of why domain is insufficient
#324
ddorwin
closed
8 years ago
1
Fix #316: Replace uses of "alerts"
#323
ddorwin
closed
8 years ago
2
Fix #315: Update headings for user informing and consent mitigation
#322
ddorwin
closed
8 years ago
1
Fix #320: Clarify that consent is required unless all recommendations…
#321
ddorwin
closed
8 years ago
1
Clarify that consent is required unless all recommendations for Distinctive Identifier clearing are implemented
#320
ddorwin
closed
8 years ago
1
Fix #314: Informing the user and requiring user consent is always per origin
#319
ddorwin
closed
8 years ago
3
Fix #313: Add step to allow user agent to return InformUser for reaso…
#318
ddorwin
closed
8 years ago
1
Broken links in format registry
#317
osmestad
closed
8 years ago
6
Replace uses of "alerts"
#316
ddorwin
closed
8 years ago
2
"Provide per-origin user alerts / prompts and permissions" headings do not accurately reflect the content
#315
ddorwin
closed
8 years ago
4
Fix inconsistency: Informing the user and requiring user consent is always per-origin
#314
ddorwin
closed
8 years ago
1
Add step to allow user agent to return InformUser for reasons other than use of Distinctive Identifiers
#313
ddorwin
closed
8 years ago
1
Security: Should implementations be required to inform users in cases where this is currently recommended?
#312
ddorwin
opened
8 years ago
11
Previous
Next