- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Sep 2022 21:14:28 +0000
- To: public-css-archive@w3.org
So in the interest of resolving this in our next meeting, I propose we choose among these options: * Generically add a `-logical` and `-physical` suffix (or `-l` and `-p`?) to all these ambiguous properties. The switch, when it's defined, causes the ambiguous property name to *parse* as the more specific version. (That is, if `@property-type logical;` is set, then writing `margin` is *exactly equivalent* to writing `margin-logical`. If you use the OM with the ambiguous property (reading or writing `style.margin`) you get the default, unswitched behavior. * Generically add a `!logical` and `!physical` suffix to all properties. (For non-ambiguous ones, it does nothing.) The switch, when it's defined, treats props without the ! as having the appropriate one. If you read from the OM, you get the default behavior. (If you write, you can set the bang in `.setProperty()`.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1282#issuecomment-1249822796 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 September 2022 21:14:30 UTC