You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AFAIK the point of this sentence was to exclude pseudo-elements, since in JS you can't use ResizeObserver to observe pseudo-elements.
The thing is, on both Blink and WebKit, Element is a superclass of PseudoElement, so pseudo-elements are perfectly capable of being ResizeObserver targets, it's just that an author doesn't have access to the PseudoElement.
So in fact, pseudo-elements can already have a last remembered size on Blink and WebKit.
On Gecko they can't, but Gecko doesn't even use ResizeObserver to track the last remembered size, so the restriction seems pointless anyways.
If pseudo-elements need to be excluded it might be because their lifetime is not completely clear, but that's a completely different topic. By itself, I don't think that not being possible ResizeObserver targets justifies not having a last remembered size.
https://drafts.csswg.org/css-sizing-4/#last-remembered
AFAIK the point of this sentence was to exclude pseudo-elements, since in JS you can't use
ResizeObserver
to observe pseudo-elements.The thing is, on both Blink and WebKit,
Element
is a superclass ofPseudoElement
, so pseudo-elements are perfectly capable of beingResizeObserver
targets, it's just that an author doesn't have access to thePseudoElement
.So in fact, pseudo-elements can already have a last remembered size on Blink and WebKit.
On Gecko they can't, but Gecko doesn't even use
ResizeObserver
to track the last remembered size, so the restriction seems pointless anyways.If pseudo-elements need to be excluded it might be because their lifetime is not completely clear, but that's a completely different topic. By itself, I don't think that not being possible
ResizeObserver
targets justifies not having a last remembered size.The text was updated successfully, but these errors were encountered: