- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 May 2023 16:33:20 +0000
- To: public-css-archive@w3.org
Okay, here's my proposal for an updated `<position>` that allows logical keywords: ``` <position> = [ [ left | center | right | x-start | x-end ] || [ top | center | bottom | y-start | y-end ] | [ left | center | right | x-start | x-end | <length-percentage> ] [ top | center | bottom | y-start | y-end | <length-percentage> ]? | [ [ left | right | x-start | x-end ] <length-percentage> ] && [ [ top | bottom | y-start | y-end ] <length-percentage> ] | [ block-start | block-end | center ] || [ inline-start | inline-end | center ] | [ start | end ]{2} | [ [ block-start | block-end ] <length-percentage> ] && [ [ inline-start | inline-end ] <length-percentage> ] ] ``` The logical additions are: 1. You can use a one or two logical keywords, or the full 4-value form with logicals. 2. To make it easier to refer to corners, you can specify a pair of `start`/`end` keywords. (So you don't have to write out the full `block-start inline-end`, just `start end` instead.) 3. The *mixed* keywords (`x-start`, etc) are added to the list of physical keywords, specifying a physical axis and then a logical direction within that axis. 4. Using one logical keyword works the same as using one physical keyword - the opposite axis is "center". -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/549#issuecomment-1561547073 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 May 2023 16:33:22 UTC