[Bug 26074] HTML parsing algorithm doesn't allow the rt element under the rtc element.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26074

Robin Berjon <robin@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |mike@w3.org,
                   |                            |public-html-wg-issue-tracki
                   |                            |ng@w3.org
          Component|CR HTML5 spec               |HTML5 spec
         Resolution|---                         |WORKSFORME
           Assignee|robin@w3.org                |dave.null@w3.org

--- Comment #1 from Robin Berjon <robin@w3.org> ---
(In reply to Yuki Sekiguchi from comment #0)
> HTML 5 spec and its editor's draft says
> http://www.w3.org/TR/html5/syntax.html#parsing-main-inbody
> > A start tag whose tag name is "rt"
> > If the stack of open elements has a ruby element in scope, then generate implied end tags, except for rtc elements. If the current node is not then a ruby element, this is a parse error.
> > Insert an HTML element for the token.
> 
> IIUC, HTML parser doesn't allow the rt element under the rtc element.
> However, the description of rt element allows this.

Those are not references to the editor's draft, they are references to a
published snapshot. The editor's draft for 5.0 is at:

    http://www.w3.org/html/wg/drafts/html/CR/Overview.html

Furthermore, what you are pointing at is not a bug in the parsing algorithm. It
says to generate implied end tags *except* for rtc elements. This leaves
containing rtc elements open.

Here is an example of a parser change that matches the ruby behaviour:

    https://github.com/html5lib/html5lib-python/pull/126/files

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 12 June 2014 11:12:46 UTC