This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23827 - Need to add features at risk prior to entry into Candidate Recommendation
Summary: Need to add features at risk prior to entry into Candidate Recommendation
Status: RESOLVED MOVED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Encrypted Media Extensions (show other bugs)
Version: unspecified
Hardware: All All
: P4 normal
Target Milestone: CR
Assignee: Adrian Bateman [MSFT]
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-14 08:25 UTC by Adrian Bateman [MSFT]
Modified: 2016-06-06 19:40 UTC (History)
4 users (show)

See Also:

Attachments

Description Adrian Bateman [MSFT] 2013-11-14 08:25:43 UTC 
As we discuss initial implementation experience from the spec, there are some features that we think may be at risk. These features will need to be marked before CR but this bug can tracks the discussion to determine those features.
Comment 1 Adrian Bateman [MSFT] 2013-11-14 08:27:40 UTC 
Bug 20336 proposed removing the keysystem attribute from the <source> element. We decided to keep it but this may need to be marked at risk to see if people actually implement and do so interoperably.
Comment 2 David Dorwin 2015-10-29 21:28:17 UTC 
I think we can close this since this will be enforced by process and there are no such items being tracked by bugs at the moment.
Comment 3 Paul Cotton 2016-05-16 16:29:13 UTC 
I am marking this bug as RESOLVED LATER this the HTML Media Extensions WG will identify the appropriate "at risk" features (if any) when we request transition into Candidate Recommendation.

/paulc
HTML HME WG Chair
Comment 4 David Dorwin 2016-06-06 19:40:19 UTC 
This is being discussed in https://github.com/w3c/encrypted-media/issues/206.