- From: Simon Pieters <simonp@opera.com>
- Date: Mon, 04 Jun 2012 10:17:42 +0200
- To: "Anselm Hannemann Web Development" <info@anselm-hannemann.com>, Kornel Lesiński <kornel@geekhood.net>
- Cc: whatwg <whatwg@whatwg.org>
On Mon, 04 Jun 2012 09:58:52 +0200, Kornel Lesiński <kornel@geekhood.net> wrote: > Since it's impossible to introduce void element at this point It's not impossible, but we generally try to only do it when there's a container (like <video>) so it gets popped off the stack soon enough to not break the whole page in old browsers. However, when we *want* fallback, we *should* use a non-void element, because using the content as fallback is better than using an attribute as fallback: * It actually gets rendered in old browsers instead of getting ignored. * It supports rich markup (which enables e.g. tagging multiple languages, bidi, ruby, etc). <canvas> was originally implemented as a void element in Safari, but was specced as as non-void element for the above reasons. -- Simon Pieters Opera Software
Received on Monday, 4 June 2012 08:17:50 UTC