Re: [csswg-drafts] [css-shapes-2] Consider allowing `<position>` for the `from` and some other points (#10644)

I disagree it's a mistake; it reads perfectly fine, to me, to say you curve "to" some position, "using" some control points, versus curving "using" some points "to" some destination. Both seem fine in English, and read reasonably in code I think. In your code, for example, I think it would look reasonable to have *all* the commands specify their endpoint immediately so the vertical reading gives a point-to-point path, and the stuff *after* the endpoints specifies command-specific info. We allow that in `arc`, after all. (But I also don't feel *strongly* about this and am fine with a fixed order - either one - if doing so makes some other issues work a lot better.)

And, hm, if we have enforced keywords, that solves the "too many lengths in a row" by itself:

```css
clip-path: shape(from top left,
  hline by 100px,
  curve by 100px 50px to right bottom,
  curve by 50px 50px by 10% 20% by var(--x) var(--y),
  curve by 50px 50px by 10% 20% to bottom 50%,
  smooth to bottom left / to 0 0,
)
```

But if we continued to allow reordering by requiring `using`, then:


```css
clip-path: shape(from top left,
  hline by 100px,
  curve using by 100px 50px to right bottom,
  curve using by 50px 50px using by 10% 20% by var(--x) var(--y),
  curve using by 50px 50px using by 10% 20% to bottom 50%,
  smooth to bottom left / to 0 0,
)
```

Hm, kinda hate that, gotta say.

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


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

Received on Monday, 5 August 2024 23:48:49 UTC