W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2017

Re: [csswg-drafts] Please define how the various box tree fixups interact

From: Boris Zbarsky via GitHub <sysbot+gh@w3.org>
Date: Tue, 16 May 2017 22:39:38 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-301935622-1494974377-sysbot+gh@w3.org>
> I presume you mean wrapping naked ruby-internal display types

No, I mean ruby-triggered inlinization.  Gecko does in fact do all the computed display bits first, before we start doing anything with boxes, because sanity.

> and in fact prevents that from happening, because it turns into an inline

That's not what https://drafts.csswg.org/css-ruby/#anon-gen-inlinize says to do (only block-level things are inlinized, and table-cell is not block-level), and not what Firefox does.  Simple testcase (using table-row instead of table-cell because it's clearer to eyeball):

    <span style="display: ruby-text-container">
      <span style="display: table-row">First</span>
      <span style="display: table-row">Second</span>

that generates an anonymous inline-table around the two rows in Firefox, I'm pretty sure.  But that's not defined sanely in any spec, because CSS anon box creation doesn't know about new display types either....

> The Ruby draft text is old 

It claims to be dated today.  ;)  Anyway, clearly changes to the ruby draft are needed; we all agree on that, which is good.

> this is precisely what https://drafts.csswg.org/css-display/#intro says

That's pretty helpful, yes.  It would be even better if all fixup definitions linked to it so you could go from a thing you're looking at to the thing that defines how the thing you're looking at fits into the world.

And again, adding a fixup should be a sane process, which means being able to easily determine what other fixups it needs to interact with.

GitHub Notification of comment by bzbarsky
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1355#issuecomment-301935622 using your GitHub account
Received on Tuesday, 16 May 2017 22:39:45 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:12 UTC