Re: [csswg-drafts] [css-logical][css-images] flow-relative gradients (#1724)

In the call Elika argued for continuing to use `to <position>` as the spec currently does, just with the expanded `<position>` from BG 4 that allows for logical directions. However, the B&G 4 version was never updated to remove the 3-value syntax. Here's an updated version that's instead expanding on [the `<position>` syntax in V&U](https://drafts.csswg.org/css-values/#position):

```
<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> ]
|
  [ start | end | center ]{1,2}
|
  [ [ start | end ] <length-percentage> ]{2}
]
```

The logical additions are:

1. You can use a one or two logical keywords, or the full 4-value form with logicals. Only specifying one keyword copies to the other axis, rather than defaulting to center. (That is, `start` is equivalent to `start start`, as opposed to how `left` is equivalent to `left center`.)
2. 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.

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1724#issuecomment-1551809388 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 17 May 2023 17:38:44 UTC