- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Nov 2019 22:05:08 +0000
- To: public-css-archive@w3.org
@simlawr That solution would somewhat cleanly solve the current issue regarding the `-gap` properties, as authors can easily understand it. Though I believe it doesn't scale because it means that for every new property that is shared between different contexts, there needs to be an alias introduced only for the purpose of feature detection. That burdens authors, as they have to remember the aliases when doing feature detection, implementors, as they have to implement the aliases only applying in certain contexts, spec. authors because they will have to remember to add those aliases when the property is used in different contexts, and documentation writers because they will also have to cover those aliases. Unfortunately, I don't have a better solution for this. There is probably no automated way of doing this kind of feature detection. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-557711824 using your GitHub account
Received on Friday, 22 November 2019 22:05:29 UTC