- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Mar 2023 16:38:32 +0000
- To: public-css-archive@w3.org
> I'm unsure why this is bad other than the inefficiency it can introduce on some specifically crafted pages. The common case here is one repetition of style/layout. Well, depending on when this is defined to happen (which right now is "somewhere, somehow"), it can cause bogus `ResizeObserver` or `IntersectionObserver` notifications, for example (if we define it to happen at the regular "intersection observer" step). It seems at the time blink does it prevents that, but it also causes other issues like scroll events not being able to see the unskipped content etc. Which is probably fine, if it is well defined. There's also the fact that if you have two nodes, unskipping the first one might cause the second one to be unskipped as well (or skipped, but because of the remembered size shenanigans that probably doesn't matter). Seems that would still be able to cause a flash? Or various sync layout flushes, which seems rather unfortunate. > notification delivery happens synchronously, and the time at which we determine intersections is within the lifecycle (right before ResizeObserver steps). Those are rather significant behavior differences from a regular IntersectionObserver, if you ask me :) -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8542#issuecomment-1460472651 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 March 2023 16:38:34 UTC