- From: <bugzilla@jessica.w3.org>
- Date: Mon, 24 Feb 2014 13:38:06 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24731 Simon Pieters <simonp@opera.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simonp@opera.com --- Comment #4 from Simon Pieters <simonp@opera.com> --- Someone was complaining in #whatwg about this being removed and cited some page he had created that uses the media attribute as a reason to keep it. I will paraphrase in order to not single him out personally. The markup was something like this: <video controls> <source src="low.webm" type="video/webm"> <source src="low.mp4" type="video/mp4"> <source src="high.webm" type="video/webm" media="all and (fullscreen:yes)"> <source src="high.mp4" type="video/mp4" media="all and (fullscreen:yes)"> </video> (I don't remember if the media query was exactly that, but something like it.) This will always pick the low quality source and never switch to the high quality source. I think having the media attribute in the spec is a disservice because the author here thought that it would be responsive and switch to high quality when the user enables fullscreen, so the author has wasted time and is in a false sense of "I made my video responsive". By removing the media attribute from the spec, if the reaction is to implement the desired functionality with JS instead, then it will start to actually work. As to making the resource selection algorithm responsive, that would be "really complicated" like Philip said, and is very unlike how the algorithm operates today. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 24 February 2014 13:38:08 UTC