W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2007

[whatwg] Fallback behavior

From: Martin Atkins <mart@degeneration.co.uk>
Date: Tue, 13 Mar 2007 07:59:40 +0000
Message-ID: <45F659EC.90704@degeneration.co.uk>
Maciej Stachowiak wrote:
> As far as I can tell, the current spec does not adequately define how 
> fallback behavior works. Specifically, what should be done with fallback 
> content when not falling back?
> Presumably it should be parsed into the DOM, but should not render - 
> that's the de facto behavior.


<object id="movie" data="movie.ogg">
    <object id="movie" data="movie.mov">
       <object id="movie" data="movie.asf">
          <p>Blah blah movie alternative text...</p>

If these things remain in the DOM, authors will presumably need to give 
them all distinct "id" values.

Now if I want to access these things from script, such as to provide an 
alternative player UI, I need to somehow determine which one is actually 
being used in order to target it. If they're all in the DOM, I can't 
just rely on getElementById returning null for the unused cases.

What's the solution in this case?
Received on Tuesday, 13 March 2007 00:59:40 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:53 UTC