- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Mar 2023 22:48:00 +0000
- To: public-css-archive@w3.org
> Can you elaborate on that? I would have hoped we'd be able to come up with a general solution for this issue. Though I'm currently not deep enough into the layout algorithm differences to make a reasonable point here. The Grid layout algorithm invokes different algos if you have flexible lengths vs if you don't. There's not much to elaborate on, it just does different things. > Though I wonder whether there might be use cases in which authors want to mix different sums of flex values to achieve a certain effect. If we normalize the sums, this isn't possible, but if we don't normalize, both can be achieved. The effect is really weird; if they want to do something weird they can do it by hand by adding more intermediate values. I don't think there's even a moderate use-case for the behavior to be done intentionally. > Though that's also already defined in the spec. by you and even [shown in an example](https://drafts.csswg.org/css-images-4/#example-465c1bec). Or is there still something missing? Ahahaha, no, I just forgot I'd done that. Okay, good. > It could still be defined as a syntax error in Grid Not... easily. Hm. I suppose I could reuse the machinery that %s do, where it's a syntax error to mix %s with a type if the % doesn't resolve to that type. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8622#issuecomment-1483537164 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 March 2023 22:48:01 UTC