[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

Koji Ishii <kojiishi@gluesoft.co.jp> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |kojiishi@gluesoft.co.jp
         Resolution|WORKSFORME                  |---

--- Comment #3 from Koji Ishii <kojiishi@gluesoft.co.jp> ---
Robin, I think Yuki is correct.

What you replied was about the first sentence of the spec:
> 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.

The problem is in the next sentence:
> If the current node is not then a ruby element, this is a parse error.

Since rt does not close rtc, the parser must allow rtc as the current node in
the second sentence.

The current WebKit implementation allows both ruby and rtc as in the line 891
of this patch:
http://trac.webkit.org/changeset/167437/trunk/Source/WebCore/html/parser/HTMLTreeBuilder.cpp
I did this because I was primarily reading "4.5 Text-level semantics" and
"8.1.2.4 Optional tags", without reading "8.2.5 Tree construction" very well.

That indicates that 4.5 and 8.2.5 are contradicting, and will result in
different implementations by which section developer reads.

It looks to me that, in this case, 4.5 is correct.

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

Received on Thursday, 12 June 2014 12:45:22 UTC