- From: Kokomi via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Sep 2024 04:19:20 +0000
- To: public-css-archive@w3.org
It’s great to see that the CSS Working Group members are fairly evaluating the two syntaxes. @nmn! I’ve drawn a picture of the image I shared with you earlier about how I perceive the two syntaxes! This might help illustrate how developers familiar with the grid syntax see the Masonry layout and what Masonry feels like when viewed as a new layout. Please let me know if I’ve got anything wrong! --- A Masonry layout might look something like this to a developer familiar with grid syntax. When I view the Masonry layout from the perspective of a grid layout, I imagine the axis where the auto-packing feature works disappearing, and each item seems to float upwards. It feels like each item is being pulled to the top. ![grid-masonry](https://github.com/user-attachments/assets/13cb344f-89f7-4c89-ac28-ee7e989085d7) --- On the other hand, with `display: masonry`, it feels like the Masonry layout is created using two components: tracks and direction, which is a different approach from the grid. I find this approach to be simpler. In the grid, it feels like you have to pay attention to every item, but with this approach, it seems easier and more intuitive to represent the same design. ![pure-masonry](https://github.com/user-attachments/assets/d5ff3f47-58f2-4948-9e8d-087d95119961) I'm not good at drawing, so it doesn't really matter if you don't understand this. -- GitHub Notification of comment by cat394 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2378370542 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 September 2024 04:19:20 UTC