- From: Javier Contreras via GitHub <noreply@w3.org>
- Date: Thu, 02 Apr 2026 18:12:18 +0000
- To: public-css-archive@w3.org
Regarding flex wrap behavior, I am not entirely convinced that the more common use case would be "dropping". We should support it, but maybe as a toggle of some sort because otherwise it can lead to surprising and unintended behavior in a lot of common cases, where the author would be confused.
## Different behavior depending on viewport (mobile vs desktop)
```
.flex {
column-rule-color: repeat(auto, red blue);
}
```
### Viewport A (desktop)
<img width="1620" height="810" alt="Image" src="https://github.com/user-attachments/assets/dcd477aa-d924-4f65-b0bd-bbd7e4d8e785" />
### Viewport B, drop at wrap (mobile)
<img width="701" height="589" alt="Image" src="https://github.com/user-attachments/assets/36e584f4-d6de-4dc0-900f-e6b0dd8e702a" />
### Viewport B , no drop at wrap (mobile)
<img width="707" height="588" alt="Image" src="https://github.com/user-attachments/assets/aed2c8dd-aa08-4cfd-8271-f077c3692c83" />
Here is a more concrete example, but in general this dropping behavior could be surprising whenever an author wants a certain "theme" where one color of the theme can seemingly randomly disappear. They may think its a bug, and would be really difficult to debug why one color is not present at all, say on mobile. This seems like a pretty common use case to me.
```
.menu-section {
display: flex;
column-rule-color: repeat(auto, var(--bleu), var(--blanc), var(--rouge));
}
```
### Viewport A (desktop)
<img width="2076" height="1424" alt="Image" src="https://github.com/user-attachments/assets/6ee7462f-b2f1-438d-a803-966910a13038" />
### Viewport B, drop at wrap (mobile)
<img width="1662" height="1374" alt="Image" src="https://github.com/user-attachments/assets/2ec0ae57-a0d5-428f-b421-63ce4d3b013e" />
### Viewport B, no drop at wrap (mobile)
<img width="1524" height="1392" alt="Image" src="https://github.com/user-attachments/assets/42c01e08-6f59-49cf-915f-9a12c8755a76" />
In general I think the no drop at wrap model behavior follows the mental model of what a flexbox is more closely, which then doesn't lead to unexpected behavior which as a result can be hard for an author to debug, since intuitively it would probably not be the expected behavior. If the author is not intimately familiar with the gaps spec, it would seem like a bug to them that one color disappears in certain viewports.
--
GitHub Notification of comment by jav099
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13754#issuecomment-4179587813 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:12:19 UTC