#jeffreyyasskin — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #jeffreyyasskin, aggregated by home.social.
-
On the article referenced in https://mastodon.design/@julieblanc/114898215638090915, @julieblanc quoted a #TAG commentary
"Overall, we think #Masonry, #Grid, and wrapping #Flexbox should be incorporated into a unified set of properties. #Chrome’s [New Masonry Layout] proposal splits apart property sets too eagerly, but even the #WebKit [using CSS Grid] proposal seems to miss a chance to develop more-general properties. (…) #CSS 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 #antipattern. 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 #JeffreyYasskin /@jyasskin) -
On the article referenced in https://mastodon.design/@julieblanc/114898215638090915, @julieblanc quoted a #TAG commentary
"Overall, we think #Masonry, #Grid, and wrapping #Flexbox should be incorporated into a unified set of properties. #Chrome’s [New Masonry Layout] proposal splits apart property sets too eagerly, but even the #WebKit [using CSS Grid] proposal seems to miss a chance to develop more-general properties. (…) #CSS 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 #antipattern. 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 #JeffreyYasskin /@jyasskin) -
On the article referenced in https://mastodon.design/@julieblanc/114898215638090915, @julieblanc quoted a #TAG commentary
"Overall, we think #Masonry, #Grid, and wrapping #Flexbox should be incorporated into a unified set of properties. #Chrome’s [New Masonry Layout] proposal splits apart property sets too eagerly, but even the #WebKit [using CSS Grid] proposal seems to miss a chance to develop more-general properties. (…) #CSS 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 #antipattern. 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 #JeffreyYasskin /@jyasskin) -
On the article referenced in https://mastodon.design/@julieblanc/114898215638090915, @julieblanc quoted a #TAG commentary
"Overall, we think #Masonry, #Grid, and wrapping #Flexbox should be incorporated into a unified set of properties. #Chrome’s [New Masonry Layout] proposal splits apart property sets too eagerly, but even the #WebKit [using CSS Grid] proposal seems to miss a chance to develop more-general properties. (…) #CSS 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 #antipattern. 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 #JeffreyYasskin /@jyasskin)