W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2015

Re: [whatwg] New ruby elements in HTML

From: Elliott Sprehn <esprehn@chromium.org>
Date: Sat, 5 Sep 2015 10:23:48 -0700
Message-ID: <CAO9Q3iL4Wn+7D4Z8Znh099BxYpYZ=7Qq80zGqO1W+3NKxVwg2g@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: WHAT Working Group <whatwg@whatwg.org>
On Sep 5, 2015 10:20 AM, "Anne van Kesteren" <annevk@annevk.nl> wrote:
> I emailed some folks individually, but I suppose I should also make a
> note here. At least Chrome, Firefox, and Safari have extended the HTML
> parser beyond the HTML Standard with the addition of special parsing
> rules for <rb> and <rtc> elements. (And slightly changed parsing rules
> for <rp> and <rt> elements.)
> Chrome uses HTMLUnknownElement for these elements, Firefox and Safari
> use HTMLElement.

That's a Chrome bug, we shouldn't be parsing any known elements like that
as HTMLUnknownElement.

> Firefox has also changed styling for these elements.
> It's unclear to me what Edge has done.
> From this it seems pretty clear we should change the parsing rules,
> for which the first commit of https://github.com/whatwg/html/pull/101
> provides my recommended solution. It's less clear to me we should be
> changing anything else.
> --
> https://annevankesteren.nl/
Received on Saturday, 5 September 2015 17:24:21 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:35 UTC