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

[whatwg] Fallback behavior

From: Maciej Stachowiak <mjs@apple.com>
Date: Mon, 12 Mar 2007 16:47:23 -0700
Message-ID: <10C6A980-50FB-408F-9EED-B9CA2015CE5C@apple.com>

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. But I don't think the spec says that  
anywhere. Then there are weirder cases, where some element has a side  
effect other than rendering.

- should scripts in fallback content execute?
- should style elements in fallback content apply style?

There's probably others. The following test case gives different  
results between trunk WebKit and Opera on the one hand, and Firefox  
on the other hand. Although in Safari's case it is probably because  
we are throwing out the content of the canvas rather than parsing but  
not rendering.


<canvas>
<b>fallback</b>
<script>
alert('x');
</script>
</canvas>

<object data="about:blank">
<b>fallback</b>
<script>
alert('y');
</script>
</object>
Received on Monday, 12 March 2007 16:47:23 UTC

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