- From: Nico Burns via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Oct 2023 17:47:04 +0000
- To: public-css-archive@w3.org
> in case box-direction gets implemented by a browser implementing Masonry without adding support for it in Flexbox (leaving no way to detect the missing support of Flexbox with box-direction). I mean, ideally this just wouldn't happen, and the release of the property could be coordinated for all layout modes (similarly to aspect-ratio). But in this case, I don't think it would matter too much if that didn't happen: > The issue would be detecting the support in Flexbox, in case box-direction gets implemented by a browser implementing Masonry without adding support for it in Flexbox (leaving no way to detect the missing support of Flexbox with box-direction). What would be the use case for this? If you want to support older browsers that don't support `box-direction` with flexbox then you would need to set both `box-direction` and `flex-direction`. And there would be no point in doing this conditionally which would just add more code to do the same thing (as CSS will ignore properties it doesn't understand anyway). If there were properties that did require layout-mode specific feature detection then I guess it might make sense to add the ability to specify display mode to `@supports` somehow. -- GitHub Notification of comment by nicoburns Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-1779765284 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 October 2023 17:47:06 UTC