- From: <bugzilla@jessica.w3.org>
- Date: Mon, 28 Jul 2014 18:53:19 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26424 --- Comment #5 from Koji Ishii <kojiishi@gluesoft.co.jp> --- (In reply to William Chen from comment #2) > I took a quick look at some usages of <rp> on the web and it didn't take > long to find a few pages that use <rp> inside of <rt> (it doesn't help that > one of these was a ruby tutorial), and also a page that looks like it was > written to take advantage of auto-closing because it didn't use close tags. > > I didn't investigate to see how different things get rendered if we changed > the parsing rules, but I suspect that making <rp> auto-close nothing will > probably cause some comparability issues. Can you paste the links you found? The spec change caused rp to auto-close rtc, so the this bug is. But even before the new spec, rp used to auto-close rt, so I created a test at http://jsbin.com/bitohe that has: <ruby>base<rt><rp>(</rp>ruby<rp>)</rp></rt></ruby> and it does not render as ruby on Chrome, Safari, nor IE. After looking at this test results, I started to wonder, maybe this isn't as critical as I originally thought. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 28 July 2014 18:53:20 UTC