- From: Anne van Kesteren <fora@annevankesteren.nl>
- Date: Sun, 29 Jan 2006 16:41:09 +0100
I did some testing in Internet Explorer with Ruby markup using the Live DOM Viewer. Here are the results: <ruby> element This element is closed by </ruby> and <ruby>. This element is required as a container. Otherwise the following elements have no "rendering semantics". Much like with the <table> element. Internet Explorer creates a mall-formed DOM for things like: "<ruby> <p> <ruby>". Doing that you get: BODY RUBY (1) P RUBY (2) RUBY (2) Where the second of (2) is red as they are identical... Putting another <p> at the end gives you: BODY RUBY (1) P RUBY (2) P RUBY (2) This means that the previous <p> is not implicitly closed. I'm not sure if that's desired. <rb> element This element is closed by any element. <x>, </y> you name it. It has no closing tag and is entirely optional. See <http://www.w3.org/TR/2001/REC-ruby-20010531/#compatibility>. Given that I'm not sure if it is implemented in the first place. <rt> element This element is closed by </rt>, <rt>, </ruby> and <ruby>. Using </ruby> or <ruby> also closes the parent <ruby> element of <rt>. <rp> element This element is closed by </rp>, <rp>, </rt>, <rt>, <ruby> and </ruby> Same as with <rt>. <rtc> element <rbc> element Both are unsupported and treated as unrecognized elements. -- Anne van Kesteren <http://annevankesteren.nl/>
Received on Sunday, 29 January 2006 07:41:09 UTC