[Webkit-unassigned] [Bug 44515] Use ruby specific 'display' property values as per HTML5 spec

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=44515

Tim Nguyen (:ntim) <ntim at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ntim at apple.com

--- Comment #9 from Tim Nguyen (:ntim) <ntim at apple.com> ---
(In reply to Dave Hyatt from comment #2)
> The problem here is that ruby can work as both an inline or block construct
> (or even as an inline-block construct).  A single display type, "ruby", is
> insufficient to model this.  The CSS3 Ruby draft has huge flaws, and if
> you're basing your HTML5 test suite off it, then you need to fix your test
> suite.
> 
> I think the HTML5 spec should be amended to drop all mention of unique Ruby
> display types until problems like this can be addressed.
> 
> The ruby-base and ruby-text display types are fine, but the Ruby display
> type needs to be broken into two display types.  We'd be willing to break
> the inline-block version of Ruby since it would rarely be desired, but I
> don't think we want positioning or floating a ruby to suddenly turn off its
> ruby behavior. Therefore block-level ruby has to be specifiable.

CSS display module level 3 addresses this by separating display into outer display and inner display.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220802/dee27eaa/attachment.htm>