Re: [csswg-drafts] [css-sizing-4] Scrollbars when intrinsic-width is > width? (#4415)

The CSS Working Group just discussed `[css-sizing-4] Scrollbars when intrinsic-width is > width?`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-sizing-4] Scrollbars when intrinsic-width is > width?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4415#issuecomment-614345165<br>
&lt;dael> fantasai: Does the phantom content area thing also effect scrolable area? If it does only the contained element or also contents outside of the element?<br>
&lt;dael> TabAtkins: Cases for first is your container is 100px.100px and overflow:auto Set contain-intrinisc-size to 200x200 We say you did your child and results in 200x200 and you ahve scrollbars. We believe you shouldg et them. Objections in issue were from a previous definition<br>
&lt;dael> TabAtkins: If you have overflow:visible and contain-intrinisic-size to be overflowing value does it set scrollbars elsewhere<br>
&lt;dael> AmeliaBR: Clarification: does the contain-intrinsic-size otherwise trigger containment or are you expected to set type and than size?<br>
&lt;dael> TabAtkins: ONly applies if size-containment is on<br>
&lt;dael> AmeliaBR: So it's separate prop. Doesn't size-containment already have effects on if your'e triggering scrollers on ancestors?<br>
&lt;dael> TabAtkins: No, layout does.<br>
&lt;dael> AmeliaBR: My intist is keep it as simple as possible and require containment property to spec any trapping of scrolling and whatever<br>
&lt;dael> TabAtkins: So it shoudl cause overflow in those cases?<br>
&lt;dael> AmeliaBR: Behave same as if child contents had been layed out and generated that intrinsis size<br>
&lt;dael> vmpstr: Combined with actual child content? Union of 2?<br>
&lt;AmeliaBR> s/intist/instinct/<br>
&lt;dael> TabAtkins: For scrollbars calc yes. It does get combined with actual children<br>
&lt;dael> ??: When you say calc scrollbars do you mean prsense? Scrollbars can effect size.<br>
&lt;fantasai> s/??/biesi<br>
&lt;dael> TabAtkins: Scrollbars don't increase size of element, jsut content<br>
&lt;cbiesinger> s/biesi/cbiesinger/<br>
&lt;dael> AmeliaBR: Came up on issue, is intrinsic with or w/o size of scrollbard. Do you add it on top?<br>
&lt;dael> TabAtkins: Scrollbars decrease size of content area.<br>
&lt;dael> cbiesinger: It can in the block axis. [missed]<br>
&lt;cbiesinger> s/missed/it can also get larger in the inline axis, at least in chrome, if it is shrinkwrapped-sized/<br>
&lt;dael> TabAtkins: Can't be the case...wait...if you turn on overflow scroll than scrollbar adds to content area. If you have overflow auto that will never increase area in a way problematic here.<br>
&lt;dael> TabAtkins: Only time it will trigger is if you have fixed height<br>
&lt;dael> cbiesinger: Auto height and you set multiplier overflow in inline axis increases size in block axis<br>
&lt;dael> Rossen___: Only if height is fixed so it is stable<br>
&lt;dael> cbiesinger: Why is height fixed<br>
&lt;dael> Rossen___: b/c for intrinisic size purpos you always fit if auto<br>
&lt;dael> fantasai: Scrollbars increase in opp size of scroll. cbiesinger Is correct<br>
&lt;dael> TabAtkins: So yes, if you trigger scrollbar on bottom of element the height would be contain-intrinsic-size height + scrollbar<br>
&lt;Rossen___> q?<br>
&lt;dael> cbiesinger: Still doesn't matter if has to be union b/c you don't know actual content size. If guess that's the answer is you don't use the union for purpose of scrollabel<br>
&lt;dael> TabAtkins: Yeah.<br>
&lt;cbiesinger> s/scrollabel/scrollbar presence/<br>
&lt;dael> TabAtkins: Actual content should not effect the size for purpose of telling if have scrollbars...i guess...once you do...<br>
&lt;dael> TabAtkins: Back up. I think this is a diversion. Need to answer, but I don't think effects current q. Should ctonain intrinsic size if larger than spec size trigger scrollbars<br>
&lt;dael> AmeliaBR: I think my argument is same, it should behave same as if you had one child element of that size and anything about scrollbars fall out of that<br>
&lt;dael> cbiesinger: So aginst using union of actual size and contain-intrinisic-size?<br>
&lt;dael> AmeliaBR: Whole point of cis is replace calc actual size of child content<br>
&lt;dael> florian: Not sure it's eq. If regular block yes, but multicol for example...<br>
&lt;dael> TabAtkins: She mispoke. It's the result of laying out your content.<br>
&lt;dael> AmeliaBR: Yeah.<br>
&lt;dael> TabAtkins: Not on children, it's just easy to say accidently<br>
&lt;dael> Rossen___: We're about 5 minutes before and fantasai wanted to go over F2F. Can we close on this or continue in issue?<br>
&lt;dael> TabAtkins: There's further detail question, but shoudl not effect how actual content of a contain-size elemtn. If actual content can pop a scrollbar that will continue to. If can't will continue.<br>
&lt;dael> florian: TabAtkins I stopped watching on GH a while back. Your assertion that my concern used to be valid I don't rmemeber. Can I jsut trust you?<br>
&lt;dael> TabAtkins: I think you can. It was about images not triggering scrollbars.<br>
&lt;dael> fantasai: I suggest we pick this up later and do F2F<br>
</details>


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

Received on Wednesday, 22 April 2020 16:56:55 UTC