- From: Stephen Chenney via GitHub <sysbot+gh@w3.org>
- Date: Sat, 01 Feb 2025 14:26:24 +0000
- To: public-css-archive@w3.org
I really appreciated the thorough discussion at the F2F and it helped a lot. I support the item-blah properties and would wait until we sort that out before deciding finally on the switch. After listening and thinking, there doesn't seem to be any strong reason to favor one approach over the other (`display` vs property). Each side has reasonable arguments, I don't think the developer ergonomics are different enough to force a decision. So how to come to agreement after many years of discussion? Browser performance and binary size comes to my mind. Could implementors comment on how often they would write `if (display == grid || display == masonry) ` in layout code vs `if (someProperty == doMasonry)` in layout code? If the former, in which more code is common between masonry and grid, then make the property the switch. If the latter, where more code differs between layout and grid, then use display as the switch. Sorry if this has been considered already, but it did not come up in the latest discussion. -- GitHub Notification of comment by schenney-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11243#issuecomment-2628973684 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 1 February 2025 14:26:25 UTC