- From: Christophe Coevoet via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Oct 2023 17:31:49 +0000
- To: public-css-archive@w3.org
@nicoburns the issue is not about detecting support for it in Masonry, where the support should be detected for Masonry itself indeed. 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). Properties shared between multiple layouts would require these rules to be feature detectable properly: - the browser release that adds support for a property must add support for this property in all existing layouts supported by the browser, to avoid situations of partial support that cannot be detected - when adding a new property that is meant to affect multiple layouts, this should be specified for all of them when introducing the new property (otherwise the previous point become impossible to satisfy by browser vendors without a time-machine to change older versions that introduced the support...) However, I have no idea how realistic enforcing those here. `margin` and `padding` were there before the introduction of the various layout modes (at least the ones that came at a time where compatibility with `@supports` makes sense), so supporting them was part of the initial spec of those layouts. And `aspect-ratio` was specified taking into account its impact on all layout modes, allowing to follow the rules above. -- GitHub Notification of comment by stof Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-1779743062 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:31:51 UTC