- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Aug 2024 08:31:12 +0000
- To: public-css-archive@w3.org
Yea, `using by` or `with by` doesn't read well... and my issue with having the control points after the end point was not so much about readability, but that it's ambiguous where `by` starts from, the end point or the start point? e.g. you have to read the docs to understand what `curve by 100% 100% using -10px -10px` does. I guess if we allow `segh` / `segv` like in #10667 it does make a bit more sense to have the end point first, but I think it's a solvable problem. e.g.: `curve by 10segh 30segv by 80px 80px` can be interpreted as `seg=0,0` when computing the next point, and then recomputed to the actual segment width/height when computing the control point. So until now I don't see a better alternative than: - ordered, control points first - explicit `by`/`to` with every point - with `by`, each control point starts from the previous point that is not `seg***`. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10644#issuecomment-2270693601 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 August 2024 08:31:13 UTC