- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Sep 2022 14:50:38 +0000
- To: public-css-archive@w3.org
@vmpstr It's observable if you later turn it into a block, i.e.
```html
<div id="test">
<div style="width: 100px; height: 100px"></div>
</div>
<script>
function nextRendering() {
return new Promise(resolve => {
requestAnimationFrame(() => requestAnimationFrame(() => resolve()));
});
}
(async () => {
// No last rememebered size yet
test.style.cssText = "width: max-content; height: max-content; contain-intrinsic-size: auto 1px";
await nextRendering();
// Now the last remembered size is 100x100
test.style.display = "inline";
await nextRendering();
// Does the last remembered size become 0x0 or preserve the old 100x100?
test.style.display = "block";
test.style.contentVisibility = "hidden";
console.log(test.clientWidth, test.clientHeight); // ???
})();
</script>
```
IMO there are two reasonable possibilities:
1. Treat inlines as being 0x0, and record that size as usual
2. Do not record the size of an inline, like in the `display: none` case
Chromium and Firefox are currently doing 1.
--
GitHub Notification of comment by Loirooriol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7606#issuecomment-1238260896 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 September 2022 14:50:39 UTC