- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Tue, 14 Jul 2009 22:05:00 +1200
On Tue, Jul 14, 2009 at 9:46 PM, Boris Zbarsky <bzbarsky at mit.edu> wrote: > For the current model, note that all the text says is "should not show this > content to the user". While this is not defined anywhere, it doesn't seem > to indicate that the content's DOM should not exist, for example. In Gecko, > at least, the image in your example will be loaded and hence its onload will > fire. > There's actually a fairly major related problem here. We hide the fallback content by treating it as display:none. Currently Gecko has a huge bug where a display:none plugin does not load/run. This works out well for the video fallback case. If we fix that bug, then unless we do some special magic, plugin-based video fallback will run and play audio while the <video> element plays --- very bad. People have already discovered that <video src="hellokitty.ogv"><object data="hellokitty.ogv"></object></video> plays the audio track twice in Firefox, and aren't happy about it, although it's what the spec seems to suggest. I'm not sure how to modify the spec in a sane way to fix this case, though. Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090714/cee4f97b/attachment.htm>
Received on Tuesday, 14 July 2009 03:05:00 UTC