00:01 | <Domenic> | Thanks. We got some attention to those in the meeting and it looks like they're at the top of mfreed's plate for tomorrow. |
00:04 | <gingeh> | Thank you so much! |
01:21 | <smaug> | Domenic: btw, related to SharedWorkers, I thought Chrome on Android doesn't even support them. But perhaps this unload thingie would be a reason to support? |
01:33 | <Domenic> | Yep, it would be, indeed. |
05:02 | <gingeh> | * Here's all the open bugs affecting my implementation in Ladybird: https://github.com/whatwg/html/issues/11007 https://github.com/whatwg/html/issues/10996 https://github.com/whatwg/html/issues/10988 https://github.com/whatwg/html/pull/9457 edit to add: https://github.com/whatwg/html/issues/11008 |
14:03 | <smaug> | oh my, I guess it is too late to fix https://html.spec.whatwg.org/#inner-navigate-event-firing-algorithm step 32. That is nuts |
14:03 | <smaug> | and I can possibly blame myself for not catching that in some review |
15:13 | <smaug> | Or it might not be too late. Only one implementation |
15:13 | <smaug> | ...shipping |
18:49 | <FrameMuse> | Hello, just joined, I wanted to ask something about dom rendering |
19:06 | <Valery> | This is purely an idea, but looking at Game Development I was looking for something like Object Instancing to be a part of DOM as well. I can't give exact examples where this optimization is decisive, but I certainly remember having issues with performance because of many the same elements (with the same huge trees) were presented in the document. So I want to ask what do you think about having a kind of mirroring a node, so it can be displayed multiple times while processing it only once. Or maybe this is overoptimization, not relevant? Sorry if I don't know something, thanks in advance. |
21:35 | <smaug> | I'd expect the implementation of such to slow down DOM/layout operations in the common cases. Gecko used to support (until ~2009) multiple presentations at the same time (normal + printing/print preview), and when that was removed, lots of the algorithms could be simplified quite a bit. |
22:12 | <emilio> | Depends at which layer you implement this tho... If it's just painting it might not be too bad (think of background-image: element() or so, IIRC we still support the prefixed version). But yeah, the set of use cases for exactly the same rendering might not be all that big... |
22:22 | <smaug> | Ah, right, for painting only that might be doable. https://developer.mozilla.org/en-US/docs/Web/CSS/element |