- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 May 2024 16:57:37 +0000
- To: public-css-archive@w3.org
All of the proposed solutions are not exclusive. The simplicity of `auto` or `from-element` should not be downplayed because large sites need something more powerful. The element identity matching seems to be already present to some extent in `content-visibility`, `contain-intrinsic-size`'s last remembered size, and maybe "last remembered" thing in anchor positioning. They all mention something along the lines of "if the element did X in the past, then do Y" which breaks under element thrashing. I'm not necessarily suggesting adding more breaking behavior, but I'm also not seeing a compelling reason why view transitions are different here. Is element thrashing common in "real" sites? DOM recycling is maybe a concern, but developers should know how to deal with it. I'm fine with trying ident/attr solution first, but isn't this just moving the naming problem from CSS to DOM? It doesn't at all address the "demo" cases, and the fact that a lot of DOM may already have unique ids on elements in "real world" cases seems coincidental at best -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8320#issuecomment-2108228965 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 May 2024 16:57:38 UTC