- From: <bugzilla@jessica.w3.org>
- Date: Wed, 03 Aug 2011 11:13:20 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13333 --- Comment #47 from Philip Jägenstedt <philipj@opera.com> 2011-08-03 11:13:18 UTC --- (In reply to comment #36) > (In reply to comment #33) > > In any case, I agree with Henry that we should neither destroy the parsing of > > <source> > > 'destroy parsing'? what are you talking about? Deployed content uses <source> like this: <video> <source src="video.mp4"> <source src="video.webm"> </video> The resource selection algorithm only considers child source element of <video>. If a browser changed the parsing of <source> to not be a void element, the above would be equivalent to: <video> <source src="video.mp4"> <source src="video.webm"></source> </source> </video> The second <source> element would not be considered and existing content would just not work. Changing the resource selection algorithm to consider *any* descendant <source> element would not be a good idea, as it precludes ever making spec changes like putting extra <audio> tracks inside <video>. -- 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, 3 August 2011 11:13:21 UTC