[Bug 10902] <video> element needs to support some form of DRM solution

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10902

--- Comment #36 from Philip Jägenstedt <philipj@opera.com> 2010-10-13 08:37:55 UTC ---
(In reply to comment #35)
> DRM scheme in advance in much the same way as codecs are specified. While this
> doesn't have any bearing on playability of a particular source, it does allow
> scripts or a user agent to determine playability in advance, smoothing the
> process somewhat. a "drm" parameter would seem sensible, with either  a
> globally-unique value (a URI, perhaps) as the value, or a registry maintained
> somewhere (WHATWG Wiki, perhaps, as with link relations)?
> 
> By nature, I don't believe the actual nitty-gritty of any particular scheme is
> relevant to HTML5: if a UA supports a scheme (e.g., FairPlay), it's going to be
> bound by the “rules” of that scheme; if it doesn't support it, those rules are
> irrelevant; and, of course, most schemes are container-specific, and HTML5
> doesn't specify any particular container formats, so specifying scheme detail
> would be silly (not to mention a political nightmare, and a case of the cart
> leading the horse).
> 
> Does this seem reasonable [philosophical objections to DRM in general
> notwithstanding]?

Assuming you mean canPlayType("video/ogg; drm=NoPlay") then this will have the
wrong fallback behavior in existing clients. At least both Opera and Firefox
ignore unknown parameters and would return "maybe" for this. It would be
simpler to change the media type to reflect that it uses DRM, both Opera and
Firefox will correctly report their non-support for 'video/ogg+drm'.

However, this is completely hypothetical, I suggest that the first browser that
supports DRM and wants to expose it somehow deal with the problem.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 13 October 2010 08:37:57 UTC