On 8/14/19 6:52 PM, Boris Zbarsky wrote:
On 8/14/19 12:37 PM, Mats Palmgren wrote:
This first patch set adds support for the new syntax
only, but no new box types (I'll add those separately in a bit).
In general, it seems like we should think about how to integrate this
stuff into layout in a better way than anonymous boxes everywhere. In
particular, we may want to consider changing nsIFrame such that we have it
point to a "how I look to my parent" class and a "how I manage my kids or
paint myself" class and be able to mix and match those.
I agree, but splitting up the 'display' property into three separate
keywords doesn't imply we'll implement them using anonymous boxes in
more cases than if it's just one keyword. Your point is well taken but
it's an independent issue.
I'm guessing you're thinking of the implementation of 'block ruby',
which indeed does introduce a new anonymous box (it's a block box with
anonymous ruby box inside it).
This is mandated by the Ruby spec though:
"If an element has an inner display type of ruby and an outer display type
other than inline, then it generates two boxes: a principal box of the
required outer display type type, and an inline-level ruby container. All
properties specified on the element apply to the principal box (and if
inheritable, inherit to the ruby container box)."
https://drafts.csswg.org/css-ruby-1/#block-ruby
(It makes sense to me to use two boxes in this case. I'm happy to
continue discuss that off-list I you want.)
(There are no anonymous boxes associated with any of the list-item values.)
Other browsers: Other UAs don't support this yet, AFAIK.
Do they plan to?
I don't know what their plans are. I haven't seen any public
announcements one way or another.
/Mats
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
