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: Wed, 17 May 2017 02:35:04 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-301968713-1494988503-sysbot+gh@w3.org>
> Then I'm not sure what you're referring to

I _think_ the relevant situation is this:

    <span style="display: grid"><span style="display: ruby-text-container"><div></div></span></span>

What ends up happening with the display of the `<div>`?

> A given fixup is either adjusting computed styles or adding anonymous boxes, which determines where it goes automatically.

Let's posit that.

> I think all the fixups in each category are either compatible or mutually exclusive

I think we're talking past each other.  I'm explicitly talking through what has to happen when someone adds a new fixup.  How do they make sure it's mutually exclusive or compatible with all existing ones?

But even past that, it's not clear to me that what you said is true, because nothing defines _when_ these fixups take place.  In my example above with grid and ruby-text-container, does the fixup, if any, for the `<div>` take place before or after fixup, if any, for the inner `<span>`?  Where is this ordering defined?  Are all fixups applied to a given element before any fixups are applied to its descendants, or is each fixup performed as a separate pass over the tree?

Seriously, this stuff needs to actually be defined.  What we have now is a non-interoperable mess that's not possible to implement interoperably based on what the specs actually say.  :(

GitHub Notification of comment by bzbarsky
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1355#issuecomment-301968713 using your GitHub account
Received on Wednesday, 17 May 2017 02:35:11 UTC

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