- From: <bugzilla@jessica.w3.org>
- Date: Thu, 24 Jul 2014 10:23:07 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26426 Bug ID: 26426 Summary: rb causing a parser error if current node is not ruby could break old content Product: HTML WG Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: CR HTML5 spec Assignee: robin@w3.org Reporter: kojiishi@gluesoft.co.jp QA Contact: public-html-bugzilla@w3.org CC: public-html-admin@w3.org Tree construction, The "in body" insertion mode <http://www.w3.org/TR/html5/syntax.html#parsing-main-inbody> states that: A start tag whose tag name is one of: "rb", "rp", "rtc" If the stack of open elements has a ruby element in scope, then generate implied end tags. If the current node is not then a ruby element, this is a parse error. This rule could break existing HTML + XHTML Ruby annotation content because they could use rbc tags: <ruby><rbc><rb>base</rb></rbc>... Such content will be a parse error because rb is not a direct child of ruby. Should we loosen the rule to require rb being the direct child of ruby? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 24 July 2014 10:23:09 UTC