- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Oct 2023 01:05:57 +0000
- To: public-css-archive@w3.org
> start or end can be used as a single keyword to refer to the block and inline start corner or end corner. I don't agree with this change (or the related one that lets them take a len-per), as it's different behavior from what a single keyword does in all other cases. In every other possibility, giving one keyword sets one axis and centers the other. I don't think being able to say "the start/start corner" is sufficiently important/common that literally saying `start start` is a burden and shortening to `start` is necessary. (Today you have to give two keywords to do this anyway, like `left top`, and nobody seems to be complaining about this.) > An offset can be applied to center. (like for other keywords; syntax sugar for calc(50% + <offset>) I disagree with this too. First, it seems unmotivated; I haven't seen anyone ask for this, and it doesn't close a glaring hole in the grammar so it's doesn't help technical correctness either. Second, the offsets for the existing keywords are offsets from an edge, with positive values pointing inward; whether that manifests as the value being syntax sugar for a positive or a negative term depends on which value it's for. There is no "inward" from center, tho, so there's no similar intuition to lean on. I think people can just write `calc(50% + ...)` if they need to offset from center, as they do today. > Removed redundant center from [ block-start | block-end | center ] || [ inline-start | inline-end | center ] as they are already part of the physical keywords syntax. Not redundant; your grammar disallows `block-start center`, for example. It does *duplicate* the `center center` case, but gives it the same meaning, which is fine. -------- So in all I think that means I disagree with all of your changes, and we should just use mine. ^_^ -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/549#issuecomment-1765494866 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 October 2023 01:05:59 UTC