- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Dec 2020 00:46:36 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-sizing-4] Allow specifying only one dimension for intrinsic sizing`, and agreed to the following: * `RESOLVED: Property takes 4 longhands, logical and physical, which have a normal value` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-sizing-4] Allow specifying only one dimension for intrinsic sizing<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/5432<br> <dael> vmpstr: Added contain-intrinsic-size property. Takes 2 values. Can take 1 to apply to width and height. Got feedback it can be confusing if dev only wants to spec in 1 direction<br> <dael> vmpstr: Proposal is to make c-i-s be a shorthand for additional values like c-i-with and c-i-height<br> <dael> florian: Which would have normal value<br> <dael> vmpstr: Yes. ANd b/c only during size containment it falls back to what hte size would be<br> <dael> vmpstr: Other is do we add width, height, and block sizes<br> <dael> florian: I'd go logical only. Or maybe all 4<br> <dael> vmpstr: Don't have preference. Feel like fewer is better<br> <dael> florian: I wouldn't do pshycial only<br> <dael> fantasai: Reason why physical is to be consistent with size property we end up having. Main reason we dont' have size property is naming conflict.<br> <Rossen_> q?<br> <dael> fantasai: Anticipation is size would be physical. That's why ended up making physical<br> <dael> florian: Sure. It's a mess so let's stick with the mess. Concept is reasonable and easy<br> <dael> vmpstr: Logical, physical or all<br> <dael> florian: I think what fantasai said overrides. We're in physical land<br> <dael> vmpstr: Both?<br> <dael> Rossen_: I think both<br> <dael> fantasai: There's a size property with all. If we have c-i-s with a longhand it should presumably have all<br> <dael> vmpstr: Makes sense. That's the proposal<br> <dael> heycam: Confused from comment in issue if you say c-i-s 500px shouldn't it be like none<br> <dael> vmpstr: Only takes effect during size containment<br> <dael> florian: I think it should be normal or none. Intrinsic size can be non-0.<br> <dael> vmpstr: I was giving when it would be 0. Should be defautl intrinisic width with a specified intrinsic height<br> <dael> florian: I'd go with normal. None seems to override. Normal seems to be do whatever you'd do if we didn't spec this<br> <dael> heycam: Is there a distinction where you might want to say there is no intrinsic size?<br> <dael> florian: If you want none you can say 0<br> <dael> heycam: But is that different?<br> <dael> fantasai: I think if there's overflow scroll it's different.<br> <dael> florian: I think we can resolve on normal and come back to if there's a use case for none<br> <dael> heycam: Sounds good<br> <dael> Rossen_: Sounds like we've arrived at resolution. heycam are you happy now?<br> <dael> heycam: okay<br> <dael> florian: Prop: Property takes 4 longhands, logical and physical, which have a normal value<br> <dael> Rossen_: Objections?<br> <dael> RESOLVED: Property takes 4 longhands, logical and physical, which have a normal value<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5432#issuecomment-737585853 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 December 2020 00:46:38 UTC