- From: <bugzilla@jessica.w3.org>
- Date: Thu, 20 Feb 2014 10:53:14 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24731 --- Comment #3 from Philip Jägenstedt <philipj@opera.com> --- (In reply to Ian Devlin from comment #2) > I don't see how those things are counter to each other but I will admit that > I wasn't very clear, my apologies. I will try to be clearer. > > First of all I think that the media attribute should remain in the > specification for the reasons given earlier. Secondly, it could be improved > upon to define that it should be treated just like other media queries in > that browser resizes etc. are adhered to as they change. For <source media> to be adaptive, it would require big changes to the media resource selection algorithm, which currently picks a source and sticks with it. Switching between sources mid-playback sounds really complicated, at least if you want the transition to be gapless. MSE combined with matchMedia can do it though. > >>This is going to be true of any widely implemented but unused feature that's removed from the Web platform. For example, document.createAttributeNS was > >>recently removed from Blink, but is still supported in every shipping browser I tested. Should it be added back to http://dom.spec.whatwg.org/? > I would say yes. And this particular example potentially suffers from the > same problem as media, in that people don't know about it. I for one have > never heard of it and don't know what it does (I do now after looking it up > - http://reference.sitepoint.com/javascript/Document/createAttributeNS). It sounds like you have an extremely high threshold for removing features from the Web platform. Suffice to say, (some) spec editors and implementors currently have a lower threshold, providing the occasional chance to simplify the platform. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 20 February 2014 10:53:15 UTC