Re: [whatwg] New ruby elements in HTML

2015-09-05 Thread Elliott Sprehn
On Sep 5, 2015 10:20 AM, "Anne van Kesteren"  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  and  elements. (And slightly changed parsing rules
> for  and  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/


[whatwg] New ruby elements in HTML

2015-09-05 Thread Anne van Kesteren
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  and  elements. (And slightly changed parsing rules
for  and  elements.)

Chrome uses HTMLUnknownElement for these elements, Firefox and Safari
use HTMLElement.

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/