Re: [csswg-drafts] [css-sizing] percentage [max-]width|height and intrinsic sizes

The CSS Working Group just discussed `percentage [max-]width|height and intrinsic sizes`.

<details><summary>The full IRC log of that discussion</summary>
&lt;astearns> topic: percentage [max-]width|height and intrinsic sizes<br>
&lt;dbaron> github: https://github.com/w3c/csswg-drafts/issues/765<br>
&lt;tantek> TabAtkins: intrinsic size of some elements with a % width or height<br>
&lt;tantek> fantasai: special behavior that images and form controls have<br>
&lt;tantek> fantasai: if you specify their width as a %, then their min-content size is assigned as if 0 sized<br>
&lt;tantek> fantasai: so this behavior has not been spec'd anywhere and should be spec'd<br>
&lt;tantek> fantasai: the one open consideration, form controls did not do this for max-width, but images did. so images responded to max-width, but form controls didn't<br>
&lt;tantek> fantasai: TabAtkins and I decided to do min and max for both images and form controls<br>
&lt;tantek> fantasai: e.g. you hav especiied  mx widht % on a form control. the form control is inside shrink-wrapped container, and the form conrol is affecting the size of the shrink-wrapped container<br>
&lt;tantek> fantasai: seems like a really obscure case and I haven't found any. there may be some out there<br>
&lt;tantek> fantasai: after talking with dbaron it seems that would be ok. want wg resolution to make changes to the spec<br>
&lt;fantasai> s/e.g./the only affected case would be/<br>
&lt;tantek> s/hav especiied  mx widht/have specified max width<br>
&lt;tantek> astearns: I want to see the changes in the spec so we can see them in the spec<br>
&lt;tantek> astearns: and discuss them there<br>
&lt;tantek> dbaron: to be clear, the thing that browsers do today isn't in the spec<br>
&lt;tantek> dbaron: tab &amp; fantasai are proposing something simpler but still fairly consistent<br>
&lt;tantek> astearns: are you interested in changing your behavior?<br>
&lt;tantek> dbaron: willing to. have been running with a patch and haven't found anything broken yet<br>
&lt;tantek> dbaron: other part hard here is defining replaced elements<br>
&lt;tantek> TabAtkins: apparently a commit went in today to HTML to define them<br>
&lt;tantek> fremy: on some we are even more inconsistent<br>
&lt;tantek> fantasai: for the sake of sanity we'd like to have ...<br>
&lt;TabAtkins> https://github.com/whatwg/html/pull/2857 PR to define replaced elements<br>
&lt;fantasai> s/.../consistency/<br>
&lt;tantek> fremy: e.g. video element with a slider<br>
&lt;tantek> fremy: all browser but edge, the default size of the contol<br>
&lt;tantek> fremy: meanwhile in edge, default size of 0<br>
&lt;fantasai> Proposed text is "However, in the case of a replaced box with a percentage-based width/max-width/height/max-height, the percentage is resolved to zero when calculating the min-content contribution in the corresponding axis."<br>
&lt;fantasai> in https://drafts.csswg.org/css-sizing/#intrinsic-contribution<br>
&lt;tantek> fantasai: we're not ...<br>
&lt;fantasai> s/fantasai: we're not ...//<br>
&lt;tantek> fremy: there was a slider for the video element which was sized with max-width %<br>
&lt;tantek> fremy: in edge since do we apply ... to this size, the minimum size was ... px, and the author provided size was 41px<br>
&lt;tantek> fremy: in other browsers, they just use the normal default size of the control which was bigger than 41px<br>
&lt;tantek> fremy: I do believe the edge behavior is what the author wanted<br>
&lt;tantek> astearns: if we take this change then ...<br>
&lt;tantek> fremy: all browsers will behave as edge is behaving<br>
&lt;fremy> beam.pro<br>
&lt;tantek> astearns: any objections to taking this change?<br>
&lt;tantek> dbaron: FWIW I just checked the WHATWG HTML dfn and it's not the one we want<br>
&lt;tantek> dbaron: it's the stricter one<br>
&lt;fremy> well, the website has been redesigned<br>
&lt;tantek> dbaron: it doesn't count form elements<br>
&lt;tantek> dbaron: only images, iframes, input type=image<br>
&lt;dbaron> and a bunch of other things<br>
&lt;tantek> astearns: I'm hearing no objection to making the change<br>
&lt;fantasai> I think we need to add "(including form controls)" here<br>
&lt;tantek> astearns: RESOLVED: take the change "However, in the case of a replaced box with a percentage-based width/max-width/height/max-height, the percentage is resolved to zero when calculating the min-content contribution in the corresponding axis."<br>
</details>


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

Received on Wednesday, 2 August 2017 14:41:57 UTC