- From: Philip Rogers via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 May 2024 15:20:11 +0000
- To: public-css-archive@w3.org
> does chromium run the whole lifecycle update for SVG images? Chrome does run most of the steps for a full animation frame (see: [SVGImage::PaintRecordForCurrentFrame](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/svg/graphics/svg_image.cc;drc=7287f0f8504645863185b9b0b1336d30f99945ed;l=385)), but steps like resize observer are no-ops. Chrome isn't calculating real user viewport intersection for images though, and is just treating the image contents as relevant to the user, regardless of whether the image is on screen. Offscreen content brought on-screen via a filter is considered relevant to the user ([spec](https://drafts.csswg.org/css-contain/#close-to-the-viewport)). I think `ctx.drawImage` should work similarly. -- GitHub Notification of comment by progers Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10347#issuecomment-2125069770 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 May 2024 15:20:12 UTC