- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Mon, 23 Feb 2015 16:10:39 -0500
- To: Xidorn Quan <quanxunzhen@gmail.com>, www-style list <www-style@w3.org>
On 02/23/2015 05:18 AM, Xidorn Quan wrote: > On Mon, Feb 23, 2015 at 8:42 AM, Xidorn Quan <quanxunzhen@gmail.com <mailto: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. > > > But one problem I'm concerned about changing the default stylesheet is that, if we change it to something like "ruby > rb { > display: ruby-base; }" then the author would be confused when he wants to override the rule. Simple rule like "rb { display: > inline; }" won't have any effect. Personally I think it would be nice if <rb>B<rt>A</rt> just worked. :) It's much more convenient to type. But to match HTML, specificity in the UA style sheet has no effect wrt author rules, so changing the rules won't be a problem. I'll update the spec. Let me know if it seems correct. ~fantasai
Received on Monday, 23 February 2015 21:11:22 UTC