- From: <bugzilla@jessica.w3.org>
- Date: Wed, 15 Jun 2011 11:57:04 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12935 --- Comment #20 from Simon Pieters <simonp@opera.com> 2011-06-15 11:57:02 UTC --- (In reply to comment #19) > Going to escalate this to the tracker, I'm afraid. As I said, I have no > opinions on whether complex ruby is something we want to add, but I'm opposed > to us foreclosing the option now due to an auto-closing behavior whose benefits > are somewhat dubious to start with. > > Tracker issue title: "HTML parsing spec should not prevent future > implementation of complex ruby or other development or ruby markup". > > Tracker issue text: "The current behavior of <rt> closing all ancestor tags up > to the <ruby> is not compatible with the existing complex ruby proposals, nor > with the paragraph-level markup suggestions from comment 9". The spec was changed already. <rt> doesn't close all ancestors up to <ruby> anymore. http://html5.org/tools/web-apps-tracker?from=6215&to=6216 -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 15 June 2011 11:57:05 UTC