| 04:43 | <Joseph__Silber> | TabAtkins, assuming the following flexbox: `flex-direction: column; flex-wrap: wrap`, is it possible to specify on one of the the items that it should be the last in its column, forcing the next element to the next column? |
| 04:44 | <Joseph__Silber> | If the flexbox were flowing in a row direction, simply setting an item to `width: 100%` would force it on its own row. But there's obviously no `height: 100%`. So, is it possible any other way? |
| 04:45 | <astearns> | There are proposed wrap-before and wrap-after properties that would do what you want. |
| 04:46 | <Joseph__Silber> | Yeah. Those are a ways off. |
| 04:46 | <astearns> | Yep |
| 04:46 | <Joseph__Silber> | Can nothing similar be achieved? |
| 04:46 | <Joseph__Silber> | Like with `width: 100%` on row-flowing flexboxes... |
| 05:07 | <MikeSmith> | join #fpc |
| 05:08 | <MikeSmith> | oofs |
| 05:11 | <TabAtkins> | gsnedders: Heavily, unfortunately. I've mostly abstracted away the operations I use behind a pseudo-DOM API (because the lxml API blows), but I heavily use CSSSelect, which relies on lxml's XPath support. |
| 05:11 | <TabAtkins> | nox: WebIDL is the next spec I plan to move to Bikeshed, but it'll be a big annoying job so I've been putting it off. ^_^ |
| 05:13 | <TabAtkins> | Joseph__Silber: You can use the width:100% trick to say that something should be the *only* thing in its row/column (the flex container has to have a definite height for this to work for column flexboxes, or else the 100% won't resolve to anything useful), but that's it. The wrap-* properties are the best you can do otherwise, to the best of my knowledge. |
| 05:13 | <TabAtkins> | (And they don't exist yet, for the purpose of flexbox.) |
| 05:13 | <Joseph__Silber> | Short answer: impossible? |
| 05:13 | <Joseph__Silber> | With a variable height flexbox. |
| 05:14 | <TabAtkins> | Probably, yeah. |
| 05:14 | <TabAtkins> | Tho I've been surprised by people's ingenuity before. |
| 07:00 | <astearns> | for keeping a flex item alone in its column, what about a flex-basis of a gazillion pixels and a flex-shrink of 1? |
| 08:50 | <annevk> | Domenic: I think that issue is about adding data-noexport="" to some of the mentioned <dfn>s |
| 08:51 | <annevk> | Anyway, back to being in hiding |
| 08:52 | <nox> | TabAtkins: How is such a move done? |
| 13:46 | <TabAtkins> | nox: With a lot of annoying slog manually converting everything. |
| 14:22 | <gsnedders> | TabAtkins: I do wonder if at some point it's worthwhile to just fork ElementTree and add more features to it, like parent access |
| 14:24 | <TabAtkins> | Do that + support selectors somehow and I can use it. 😀 |
| 14:45 | <Joseph__Silber> | astearns, The viewport's height can be a gazillion pixels. It can stretch indefinitely. I don't see how using a humongous flex-basis will help. |