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 26949 - video: Contradiction between Shadow DOM spec and HTML 5 spec
Summary: video: Contradiction between Shadow DOM spec and HTML 5 spec
Status: RESOLVED DUPLICATE of bug 26952
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 major
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 26952
  Show dependency treegraph
 
Reported: 2014-10-01 17:09 UTC by Dylan Barrell
Modified: 2014-10-07 09:10 UTC (History)
5 users (show)

See Also:


Attachments

Description Dylan Barrell 2014-10-01 17:09:02 UTC
There is a conflict between this restriction

"Dynamically modifying a source element and its attribute when the element is already inserted in a video or audio element will have no effect. To change what is playing, just use the src attribute on the media element directly, possibly making use of the canPlayType() method to pick from amongst available resources. Generally, manipulating source elements manually after the document has been parsed is an unnecessarily complicated approach."

and the shadow DOM distributions spec

http://w3c.github.io/webcomponents/spec/shadow/#distributions

that results in the video tag not being able to be constructively used inside a web component

Example here: http://jsfiddle.net/n88owmop/4/
Comment 1 Philip Jägenstedt 2014-10-03 13:32:14 UTC
I don't quite understand the problem, can you elaborate? Is the problem that the <source> element won't become the direct child of the <video> element because of however <template> and <content> work?
Comment 2 Dylan Barrell 2014-10-03 15:06:35 UTC
The discussion has moved on to here;

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26952
Comment 3 Philip Jägenstedt 2014-10-07 09:10:27 UTC

*** This bug has been marked as a duplicate of bug 26952 ***