| 00:01 | <MikeSmith> | ah OK for setInterval() case, the spec just omits the `subdfn` flag from the markup for the subsequent method descriptions |
| 00:01 | <MikeSmith> | so I'll just do that |
| 05:41 | <Domenic> | MikeSmith: what does subdfn even do? :-/ |
| 07:57 | <MikeSmith> | Domenic: I wish I could claim I knew 😆 |
| 14:43 | <Domenic> | MikeSmith: thanks so much for your help burning down these fixes :D |
| 14:47 | <annevk> | I guess I should have known something was up sooner when everything started passing the build script... I sorta assumed everyone was just building before submitting a PR... Though I guess even if they were they wouldn't catch anything either |
| 14:55 | <Domenic> | Dang there are a lot of good bugs trapped in https://www.w3.org/Bugs/Public/buglist.cgi?bug_status=__open__&component=HTML5%20spec&list_id=61028&product=HTML%20WG |
| 14:57 | <annevk> | Domenic: file an issue maybe so we don't forget? Although it's hard to prioritize relative to all the other bugs we have 😟 |
| 19:36 | <JosephSilber> | TabAtkins, adding `max-width` to the cross axis of a flex item removes its intrinsic width. |
| 19:36 | <JosephSilber> | http://i.imgur.com/DxYzcWR.png |
| 19:36 | <JosephSilber> | Any way to get it back? |
| 19:37 | <JosephSilber> | Here's a fiddle: http://codepen.io/anon/pen/wMWBgy?editors=110 |
| 20:30 | <TabAtkins> | ondras: They are the same, except flex-basis: auto means "look at width/height instead". flex-basis: content means the same as width: auto. |
| 20:30 | <TabAtkins> | (Don't ask, we made an early mistake and it was too late once we realized to fix it right.) |
| 20:54 | <JosephSilber> | TabAtkins, was that supposed to be targeted to me? |
| 21:03 | <ondras> | TabAtkins: I see. So perhaps I shall rephrase my question to "why do I need an explicitly set dimension (i.e. height:0) to change the sizing behavior?" |
| 21:05 | <TabAtkins> | ondras: You don't. However, setting a height has some side-effects that happen to be similar to the correct behavior in a lot of simple cases. |
| 21:06 | <TabAtkins> | In particular, if you have a column flexbox, and the flex item overflow:visible, the default min-height:auto prevents it from getting smaller than its normal layout height. |
| 21:07 | <TabAtkins> | min-height:auto pays attention to an explicit height, tho - setting "height:0" makes "min-height:auto" act like "min-height:0", so you can flex upwards from zero. |
| 21:07 | <TabAtkins> | You can also just set "min-height:0" to make it start at its normal height, but allow shrinking. |
| 21:07 | <TabAtkins> | (That's the "correct" method.) |
| 21:07 | <TabAtkins> | JosephSilber: No, haven't looked into your issue quite yet. |
| 21:08 | <TabAtkins> | (Was on my phone earlier.) |
| 21:08 | <JosephSilber> | Ok. No pressure. Thanks for looking at it... |
| 21:09 | <TabAtkins> | JosephSilber: What do you mean by "removes its intrinsic width"? What do you think should happen in that pen? |
| 21:11 | <JosephSilber> | TabAtkins, I want to width of `.content` to only go under 500px if the parent/viewport shrinks. |
| 21:11 | <JosephSilber> | Otherwise it should always be its max width. |
| 21:12 | <JosephSilber> | Without flexbox, `max-width: 500px; margin: 0 auto` would do the trick I'm looking for. |
| 21:12 | <TabAtkins> | And your issue is that it instead is always just the tight width of wrapping around its text? |
| 21:12 | <JosephSilber> | Correct. |
| 21:14 | <JosephSilber> | Since it's a block-level element, I assumed it'd try to expand as much as it can. |
| 21:14 | <JosephSilber> | But somehow `self-align: center` makes it shrink. |
| 21:16 | <TabAtkins> | Okay, so the max-width isn't your problem. It does exactly what you think it should. |
| 21:16 | <TabAtkins> | The issue is https://drafts.csswg.org/css-flexbox/#algo-cross-item |
| 21:16 | <TabAtkins> | Where "auto" in the cross-size property (width, in this case) is treated as "fit-content" (shrinkwrap) |
| 21:17 | <TabAtkins> | So things default to wrapping tight, like a float does. |
| 21:17 | <TabAtkins> | (If it didn't, center/etc wouldn't be all that useful.) |
| 21:17 | <JosephSilber> | What does `flex-basis` mean on the cross axis? |
| 21:18 | <ondras> | TabAtkins: thanks for the explanation. I will apparently have to read it several times before I understand how precisely this works, let me switch to min-height:0 in the meantime. Or flex:1, maybe? |
| 21:19 | <TabAtkins> | JosephSilber: Nothing. 'flex' and its subproperties only apply in the main axis, controlling flexing. |
| 21:19 | <JosephSilber> | Right. I misread that. |
| 21:19 | <JosephSilber> | I understand now why it uses `fit-content` by default. |
| 21:19 | <JosephSilber> | Is there any way I can change it? |
| 21:19 | <TabAtkins> | ondras: The important point to remember is that if you want something vertical to be able to shrink below its normal size, set 'overflow' to something other than the default "visible". |
| 21:20 | <TabAtkins> | JosephSilber: Yeah, use width:100% |
| 21:20 | <TabAtkins> | (Once the Sizing spec is more fully supported, you can use "width: fill" to explicitly invoke the "grow like a block" behavior.) |
| 21:20 | <ondras> | TabAtkins: I am using overflow:auto, yes. But with no height/min-height set, this flexible item never shrinks below its content size, not overflowing at all. |
| 21:21 | <TabAtkins> | ondras: That's problematic. overflow:auto should be fine - it's only overflow:visible that's defined to trigger the "don't shrink below your minimum size". |
| 21:21 | <TabAtkins> | There's been some behavior changes over time in this case, tho. |
| 21:22 | <JosephSilber> | So the width determines the cross-size, but I can still restrict it with a max-width. Interesting. |
| 21:23 | <TabAtkins> | JosephSilber: Just like normal, yeah. |
| 21:23 | <TabAtkins> | Literally the only difference from normal is the behavior of "width: auto". |
| 21:23 | <JosephSilber> | Yeah. I guess that makes sense. |
| 21:25 | <TabAtkins> | And like I said, sorry that it's kinda weird to get back the "fill the width" behavior. fantasai and I have been gradually fixing and teasing apart the sizing/alignment stuff, and it's taking time for browsers to backfill the keywords. |
