- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Apr 2024 23:32:09 +0000
- To: public-css-archive@w3.org
Okay, made two fixes here. 1. Closed the loophole @xiaochengh mentioned, by simply auto-failing the fallback style if it resulted in a negative-size containing block. 2. Fixed the *broken* text I accidentally introduced in ab022274, while making some unrelated fixes. (The spec was, for some reason, changed to simply subtract the snapshotted offset from both the element and the CB before comparing them. This, obviously, doesn't actually affect the comparison's result.) We're back to allowing auto insets to work "correctly" when building the IMCB, for the purpose of overflow checking. (That is, we don't eagerly turn autos into 0, likely resulting in a busted IMCB with no relation to the anchor's actual position. Instead we shift the insets by the snapshot offset, *then* resolve autos, so if the anchor is scrolled into the range of the CB, the auto inset can actually produce a non-degenerate IMCB.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8059#issuecomment-2046197719 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 April 2024 23:32:10 UTC