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

[whatwg] Fallback behavior

From: Mihai Sucan <mihai.sucan@gmail.com>
Date: Tue, 13 Mar 2007 15:13:08 +0200
Message-ID: <op.to4pn6kpmcpsjgr0b0dp@localhost.localdomain>
Le Tue, 13 Mar 2007 13:21:14 +0200, Anne van Kesteren <annevk at opera.com> a  
?crit:

> Not sure. Should
>
>    <object data=foo>
>      <img src=bar onload=alert('x')>
>
> show a modal dialog?

No, it should not. Fallback content should not execute (styling and  
scripts), also, fallback content should not be downloaded automatically  
(in the given example: "bar" should not download).

However, if <object data=foo> is not supported by the UA, then the  
fallback content must execute (styling and scripts), and, obviously, the  
"bar" image must be displayed (given UA support for such capabilities).

Last, but not least, the DOM must contain the fallback content as well. In  
the above example, <img> must be a child node of the <object> node.

UAs that have no support for the <object> and thus choose to display the  
fallback content must also provide the <object> node in the DOM, as the  
other UAs which have support. Again, <img> must be a child node of the  
<object> node.

HTML5 should eliminate this confusion, by specifically stating the  
behaviour in the case of fallback content.




-- 
http://www.robodesign.ro
ROBO Design - We bring you the future
Received on Tuesday, 13 March 2007 06:13:08 UTC

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