- From: Sam Davis via GitHub <noreply@w3.org>
- Date: Thu, 02 Apr 2026 18:14:18 +0000
- To: public-css-archive@w3.org
For flex wrapping, I do not think we should have the dropping behavior by default. This reasoning boils down to the same sentiment that motivated web authors choosing **_linear assignment_** in [issue 13663](https://github.com/w3c/csswg-drafts/issues/13663): It's not immediately clear from the CSS what to expect if dropping is the default. For example, in this [self-contained component](https://codepen.io/samdomekara/pen/qEaYzYG?__prettifying=true) I created for a notification card: <img width="385" height="186" alt="Image" src="https://github.com/user-attachments/assets/60540268-5cbf-4939-ac45-c7dd7ab13ae3" /> ```css column-rule-style: solid, dotted; ``` If dropping were the default, there would be a **_solid_** line between `Open` and `Preview` and a **_dotted_** line between `Preview` and `Remove`, which doesn’t reflect the separation I want. I understand the need for dropping behavior when items shift and certain decorations need to stay with specific groups, but I don't think it should be the default. For fragmented gaps, we should apply dropping behavior to maintain consistency when printing. -- GitHub Notification of comment by oSamDavis Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13754#issuecomment-4179598490 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 April 2026 18:14:19 UTC