- From: Chris Harvey via GitHub <sysbot+gh@w3.org>
- Date: Sat, 17 Sep 2022 03:23:43 +0000
- To: public-css-archive@w3.org
Issues with the file-level declarations, which were mentioned in the chat log above, reiterating here. 1. Minifiers and bundlers like to concatenate a bunch of CSS files into one. How will that affect the scope? 2. Sometimes you really do want physical properties. Say a certain border radius or box shadow that shouldn’t change even when writing-mode & direction are changed. This likely means a mix of physical and logical properties in your code. How would a file-level declaration affect them? How long is the list of ambiguous shorthand properties? If the list is small, is it worth adding a whole new file declaration? This might be out on a limb here, but what if there was *no support* for logical shorthands? What if they all remain physical, and if devs want logical properties they have to declare them explicitly (long-hand)? With tools like IDE code-completion and CSS preprocessors, how high is the demand for shorthand? -- GitHub Notification of comment by chharvey Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1282#issuecomment-1249988143 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 17 September 2022 03:23:45 UTC