- From: Westbrook Johnson via GitHub <noreply@w3.org>
- Date: Thu, 28 Aug 2025 11:43:53 +0000
- To: public-css-archive@w3.org
The actual use case that I am leveraging this for is virtualized scrolling. The act of having a fixed scrolling area and content that is taken on and off of the DOM as the specific area they fill comes close to the viewport (for background). For a "grid list" (fixed content size, one dimensional grid) it is working excellently. As noted in the OP `grid-column` or `grid-row` are great for placing the content where it needs to go and `grid-template-columns: repeat(var(--item-count), 100px);` does the magic of holding the content open without needing placeholder elements. For a "fixed grid" (fixed content size, fixed delivery size, two dimensional grid) the math is pretty easy to do, and the intersection of `grid-column` and `grid-row` work pretty well. I previously prototyped that, but will be moving into a more serious implementation later this week. It's the responsive sizing of the content that is a little tricky. I'd love for something like `grid-cell` to "just work". It's 100% in the explicit grid, for my use cases. And, I'd be totally fine with it being `grid-area` and it an integer being the part that signs the contract on "exactly where to go". Great suggestion on that Noah! I like the pure CSS solution, because it theorizes the ability to do less at large, but in that JS is involved in this process, I would not be opposed to it being a Grid Information API in the JS, either. Feels like a larger lift at the browser level; maybe the perception of a deeper investment in CSS advancements by browser vendors is purely experiential 🤞🏼. Have you thought of what that sort of API might look like at all? Which ever path felt most likely, I'd be happy to help work through possibilities. 🙇🏼 -- GitHub Notification of comment by Westbrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12658#issuecomment-3233163954 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 August 2025 11:43:54 UTC