Chris Harrelson

No. `content-visibility: hidden` preserves the layout objects (or more precisely, defines the elements to still have layout boxes. It's technically up to the UA whether to cache the layout objects)....

I think the other use case - [On-screen but non-interactive content](https://github.com/WICG/inert/blob/master/explainer.md#use-cases) is still unmet, and would be a use case of the `inert` keyword.

> Any chance you could share implementations of some of these so that we could look/compare? I don't have a specific implementation fo a drawer using `content-visibility:hidden` on hand to...

@npm1 (co-editor of Element Timing) is a good contact for further questions.

Thanks for the response! > Are we talking here about also rewriting the `width` and `height` properties of the image in the associated HTML resource? Not rewrite, but set if...

> * We'd be interested only if `intrinsicsize` was merely a hint, and image's actual intrinsic size took priority over the attribute. If `intrinsicsize` is an overriding directive that can...

> Is there a reason to make `width`/`heigth` dual-purpose One reason: width and height could (should?) transition over time into a best practice of being considered sizing & aspect-ratio hinting...

Here is another argument against the `sizingistentative` idea (via @eaenet): if this is only useful for middleware like CDNs, that is odd and a sign this is not a necessary...

@kornelski interesting. I hear you about the desire to have a solution that avoids such coordination.

The use-cases mentioned in #10 do sound legitimate to me. It does seem useful to query the backing size of the resource, independent of the sizing algorithm inputs. e.g. to...