| 07:08 | <annevk> | hayato: we also need your feedback for https://github.com/whatwg/dom/issues/242#issuecomment-217281317 |
| 07:08 | <annevk> | hayato: in case you missed it, in https://github.com/whatwg/html/issues/1160 we concluded we should flip the default for scoped |
| 07:11 | <hayato> | annevk: Thanks! Let me take a look soon. I am catching up. Thank you for your patience. |
| 07:11 | <annevk> | hayato: no worries, hope you had a nice break |
| 16:13 | <Yst> | I'm trying to build some code that renders XHTML, but I'm having trouble with <table/>s. In the Web browsers I've used, unless told to do otherwise, set table column widths in such a way that it minimizes table height. Does anyone have any advice as to how I'd calculate the optimum column widths to implement that? The best that I can come up with is a guess/check method that renders the table with every |
| 16:13 | <Yst> | possible combination of widths and chooses the shortest table, but that seems highly inefficient. |
| 16:17 | <TabAtkins> | Yst: Table layout is still heavily unspecified, but someone's finally starting to spec it out in https://drafts.csswg.org/css-tables/ |
| 16:22 | <Yst> | Thank you TabAtkins! I'll read over that. |
| 17:37 | <rniwa> | annevk: so the problem here is that your statement is inconsistent |
| 17:38 | <rniwa> | annevk: if we didn't care about styling of elements at all, then flatten: true option shouldn't be needed |
| 17:38 | <rniwa> | annevk: because there is nothing special about slots that are assigned to another slot |
| 17:39 | <rniwa> | annevk: if, on the other hand, we cared about slots being assigned to another slot because those assigned nodes would appear as if they're direct children of the outer slot, then that's about us caring about the styling of the inner slots which are display: contents by default |
| 19:28 | <annevk> | rniwa: perhaps it's confusing that we call it flatten and we should call it composed there too, and only the layout tree cares about flattening |
| 19:29 | <rniwa> | @annevk: yea |
| 19:30 | <annevk> | I mostly see it as getting assigned nodes recursively and taking care of fallback, not really getting the layout tree results |
| 19:30 | <annevk> | We wouldn't exclude display:none elements, for instance, either |
| 19:30 | <annevk> | So yeah, maybe getAssignedNodes({composed:true}) would be a better API and draw the boundary more clearly |
| 19:32 | <annevk> | We wouldn't exclude display:none elements, for instance, either |
| 19:32 | <annevk> | So yeah, maybe getAssignedNodes({composed:true}) would be a better API and draw the boundary more clearly |
| 19:32 | <annevk> | Ugh |
| 19:58 | <aklein> | Domenic: where does HTML set the [[HostDefined]] of the module record returned from ParseModule? I see it read at https://html.spec.whatwg.org/#hostresolveimportedmodule(referencingmodule,-specifier), but not set anywhere |
| 19:58 | <aklein> | oh, duh |
| 19:58 | <aklein> | ES sets it for you |
| 19:58 | <aklein> | nm |
| 19:58 | <Domenic> | :) |
| 20:08 | <zewt> | looks like the change that screwed up the android tracer was making the second argument to History.pushState required |
| 20:09 | <zewt> | which seems like an obviously bad change--no point in breaking pages and forcing people to pass an unneeded argument instead of just working |
| 20:17 | <zewt> | oh, that's from a previous time chrome broke systrace (last may, not this may) ... too bad, might have been able to monkey patch around that one |
| 21:00 | <rniwa> | annevk: are you still there?? |
| 21:01 | <hober> | rniwa: it's pretty late in .ch |
| 21:03 | <rniwa> | hober: it's only 10PM there, right? |
| 21:03 | <rniwa> | oh I guess 11PM? |
| 21:03 | <rniwa> | nah, I'd consider it mid-day still :P |
| 21:03 | <hober> | rniwa: hahahaha, i suppose you would |
| 21:04 | hober | would be in bed already if he were in europe |