Pierre Huyghebaert<p>On the article referenced in <a href="https://mastodon.design/@julieblanc/114898215638090915" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mastodon.design/@julieblanc/11</span><span class="invisible">4898215638090915</span></a>, <span class="h-card" translate="no"><a href="https://mastodon.design/@julieblanc" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>julieblanc</span></a></span> quoted a <a href="https://post.lurk.org/tags/TAG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TAG</span></a> commentary <br>"Overall, we think <a href="https://post.lurk.org/tags/Masonry" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Masonry</span></a>, <a href="https://post.lurk.org/tags/Grid" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Grid</span></a>, and wrapping <a href="https://post.lurk.org/tags/Flexbox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Flexbox</span></a> should be incorporated into a unified set of properties. <a href="https://post.lurk.org/tags/Chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chrome</span></a>’s [New Masonry Layout] proposal splits apart property sets too eagerly, but even the <a href="https://post.lurk.org/tags/WebKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebKit</span></a> [using CSS Grid] proposal seems to miss a chance to develop more-general properties. (…) <a href="https://post.lurk.org/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSS</span></a> currently has 3 layout modes (…): Grid, Multicol, and wrapping Flexbox. This is already causing a lot of author confusion, and Masonry attempts to add a 4th mode. As a general principle, having vastly different ways to accomplish slightly different things is a usability <a href="https://post.lurk.org/tags/antipattern" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>antipattern</span></a>. We urge the [CSS] W[orking] G[group] to explore ways to unify these so that authors can port more knowledge from one to the other (even if they are implemented as separate code paths internally). (Issue #1003 on w3ctag/design-reviews, comment on Nov 20, 2024, by <a href="https://post.lurk.org/tags/JeffreyYasskin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JeffreyYasskin</span></a> /@jyasskin)</p>