Re: [csswg-drafts] [css-sizing] add fill(<length-percentage>) / rename stretch keyword for width/height? (#5650)

The CSS Working Group just discussed `[css-sizing] add fill(<length-percentage>) / rename stretch keyword for width/height?`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic:  [css-sizing] add fill(&lt;length-percentage>) / rename stretch keyword for width/height?<br>
&lt;fantasai> I'm thinking maybe it should be called "Mapping Group" and we should call logical property group "logical property mapping group" or something...<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5650<br>
&lt;dael> fantasai: As I was going through some of sizing occured we might want to have the baility to rep the size as I want you to fill this length or %. What this would do which is different is account for margins<br>
&lt;dael> fantasai: WE have a keyword currently called stretch which should be same name as function. Gives the fill of the block element. Introduce a function which does same but fill arbitrary elements. Call it fill or stretch depending on how we name the keyword. SHould match<br>
&lt;dael> TabAtkins: Sounds reasonable to me<br>
&lt;dael> astearns: Sounds reasonable, but that's a low bar. I think I'd like to see use cases<br>
&lt;dael> fantasai: Sure. Max-heigh fill 100vh on images. Long scrolling doc with images want to make sure they're not bigger then viewport. What if you want to account for margins? You can subtract for a length but with this you can subtract the margins.<br>
&lt;dael> fantasai: We can discuss later but I think we need to decide if we want to keep stretch or fill as keyword for the overall behavior<br>
&lt;dael> chrishtr: Could you add the examples to the issue?<br>
&lt;dael> astearns: The 100vh one is.<br>
&lt;dael> astearns: I'm partial to stretch term. Fill isn't quite the meaning in my mind. I don't know if anyone else has opinion<br>
&lt;dael> oriol: I prefer to keep stretch b/c matches the keyword in justify/align-self which is same behavior w/o max width and height properties aren't taken into acocunt. Easier for authors if keep same name.<br>
&lt;dael> astearns: A little concerned about weird edge cases where stretching or accomodating margins makes things more complicated. Just a general worry this isn't as simple as stated.<br>
&lt;dael> astearns: Other opinions?<br>
&lt;dael> astearns: Shall we go back to the issue for now?<br>
&lt;dael> astearns: Since fantasai mentioned you're happy not to resolve today<br>
&lt;dael> fantasai: Yeah, I mentioned that<br>
&lt;dael> astearns: Let's keep this open and talk through more use cases and edge cases.<br>
&lt;dael> astearns: If anyone interested in drawing out impl of this that would also be useful<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5650#issuecomment-722052878 using your GitHub account


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

Received on Thursday, 5 November 2020 00:39:51 UTC