- From: Alan Stearns via GitHub <noreply@w3.org>
- Date: Fri, 23 Jan 2026 16:16:11 +0000
- To: public-css-archive@w3.org
> it's really only useful to have it in CSS if developers will actually be able to do what they're doing using the CSS features for a large percentage of the time This makes sense and I mostly agree with your reasons for coming to this conclusion. So I think we can accept some complexity if we find a way to satisfy a large percentage of the cases. But one possible way to satisfy these concerns is to target a smaller percentage of the highest-priority cases, and find a way (via naming or dev rel) to communicate the limitations so that authors know only to use it for the cases it’s designed for. This assumes we can identify what the highest-priority cases actually are, and that we can actually make the limitations clear. It also makes it difficult to extend the same mechanism to cover additional cases over time. So I think I prefer that we find a more general mechanism. I just wanted to mention an alternative fallback approach. -- GitHub Notification of comment by astearns Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13163#issuecomment-3791035183 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 January 2026 16:16:12 UTC