- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Aug 2023 22:21:39 +0000
- To: public-css-archive@w3.org
As I mentioned in the breakout, right now the spec has two types of fallback behavior: 1. Fairly simple "just flip things around to the other side" automatic fallback, opted into by the author. 2. Explicit "if the first doesn't fit, try these properties instead" arbitrary fallback via `@position-fallback`. The grid-based proposal's fallback mechanism falls between these two, at a 1.5 complexity level - it can do a little more than 1, and requires commensurately a *little* more specifying by the author, but isn't nearly as complex or powerful as 2. I think for this an exploration of use-cases would be best. This might be something that's best delayed until level 2, so we can see where the pain points are for authors in real world code, and make sure the complexity is needed. (But I'm happy to not delay if there's some reasonably convincing answers.) Afaict this could be added in the future with a minimum of pain. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9270#issuecomment-1699931054 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 August 2023 22:21:42 UTC