Re: [csswg-drafts] [css-grid-3][masonry] Drop `next` value of `masonry-auto-flow` (#10232)

I disagree, as I explained in #9988.

> This value seems to cause problems with accessibility

Please explain these problems. Sure, items close in document order can appear far away. But this can already happen with `order`, multicol, etc.

> those cases are probably better handled by the masonry-threshold idea

I disagree. `next` brings stability, if you use it you can be sure that a small change in the size of a grid item will not completely rearrange all the following items in a chaotic way. `masonry-threshold` doesn't achieve that, it just changes the threshold at which things will shuffle.

Also note that `next` is a feature exposed in multiple masonry libraries:
 - https://masonry.desandro.com/options#horizontalorder
 - https://github.com/bigbite/macy.js?tab=readme-ov-file#trueorder
 - https://mui.com/material-ui/react-masonry/#sequential
 - https://github.com/Spope/MiniMasonry.js#parameters

And it's requested by authors: https://github.com/w3c/csswg-drafts/issues/10233#issuecomment-2070148836

-- 
GitHub Notification of comment by Loirooriol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10232#issuecomment-2070780220 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 22 April 2024 19:35:11 UTC