Re: [css-ruby] Conflict with HTML5 spec

We finally decided not to conform the semantics statement in the HTML5
specs, because the stylesheet in those specs also include rules like "rt {
display: ruby-text; }", which indicate our current behavior.

Since both of the statements (the semantics one and the stylesheet) seem
not to be normative for rendering behavior, and the semantics statement is
vague while the stylesheet is clear, we think it's fine to apply those
display value unconditionally, which allows <rb>, <rt> tags have effect
even outside <ruby>.

I think the default stylesheet in the CSS Ruby spec could be changed back
to the previous version.

- Xidorn

On Mon, Feb 23, 2015 at 8:42 AM, Xidorn Quan <quanxunzhen@gmail.com> wrote:

> I just notice a conflict between the CSS Ruby spec and the sections
> related to ruby in the HTML5 spec.
>
> The HTML5 spec of both WHATWG and W3C version say that
> improperly-contained inner ruby elements should represent their children
> (Including that <rp> should not be hidden). [1][2]
>
> However, the CSS Ruby specifies the display value unconditionally to those
> tags in the default stylesheet [3], and requires generating proper parents
> for those elements [4].
>
> I guess the easiest way to fix this conflict is changing the default
> stylesheet to meet the HTML5 spec.
>
> [1] https://html.spec.whatwg.org/multipage/semantics.html#the-rt-element
> [2] http://www.w3.org/TR/html5/text-level-semantics.html#the-rt-element
> [3] http://dev.w3.org/csswg/css-ruby-1/#default-ua-ruby
> [4] http://dev.w3.org/csswg/css-ruby-1/#box-fixup
>
> - Xidorn
>