- From: Michael A. Puls II <shadow2531@gmail.com>
- Date: Tue, 14 Jul 2009 04:32:45 -0400
On Mon, 13 Jul 2009 17:23:47 -0400, Michael A. Puls II
<shadow2531 at gmail.com> wrote:
> On Mon, 13 Jul 2009 17:01:26 -0400, Philip J?genstedt
> <philipj at opera.com> wrote:
>
>> Does audio also have fallback content?
>
> With <audio>, you can set its display to 'none' and the audio will still
> play. However, if its display is set to 'none' and the element were to
> fall back to a child object element that loads a plug-in, things
> wouldn't work because plug-ins don't work with a display of 'none'.
>
> You would then have to detect that <audio> fell back so you could set
> its display to "inline-block" for example so the fallback plug-in would
> actually load. Or, there'd have to be a new css selector to handle this
> like audio::fallback_state { display: inline-block} or a parent selector
> on the child object element that was only applied when <audio> fell back
> to it. Or, the browser would have to make plug-in objects that are
> descendants of an <audio> element work with a display of 'none'.
>
> The same applies to <video> if you want to set its display to 'none' and
> just hear the audio.
I realize that this is also a problem for fallback in browsers that don't
support <video> and <audio>. So, it's not specific to falling back in
browser that *do* support them.
--
Michael
Received on Tuesday, 14 July 2009 01:32:45 UTC