Re: [csswg-drafts] [css-ruby] Be more specific about the box model of base/annotation container boxes (#4937)

> if we agree on that ruby base / text container should have their content area wrapping the block margin of ruby base / text box, then I think it's more consistent to actually take block margin of the containers into account. This is not hard to implement. It was just that we didn't consider this as the right behavior.

To me, doing it on the base / annotations is good because it's useful, both in the inline direction and the block direction

For the base containers / annotations containers, these boxes seem mostly useful to me in the abstract sense, to figure out relationships between things, but you don't really need them as boxes in a visual sense, so I'd rather than no margin/padding/border apply at all, in either axis, and keep them as invisible glue. But if we make them more normal, and have M/B/P work in one axis, I'd rather be consistent and have them work in both axes.

> I mean leaving whether implementation needs to support border / padding of ruby base / text container unspecified.

I'd rather not, because controlling spacing between bases and annotations is a thing people want to do, and if it is possible in some browsers to do that with m/b/p on base containers or annotation containers, then sooner or later people will do it, and everybody will have to copy that behavior. So I'd rather state upfront whether they affect layout or not.

If they don't affect layout, whether you can still specify them or not and affect the painting of the background seems less important, and I'd be OK with leaving that open (as section 3.2 does).


-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4937#issuecomment-612016839 using your GitHub account

Received on Friday, 10 April 2020 12:55:26 UTC