| 07:32 | <annevk> | TabAtkins: yeah, I wish we could move those forward somehow. Pretty good win, though I don’t remember the latest there |
| 08:04 | <annevk> | domfarolino: what's the status of https://github.com/whatwg/html/pull/3752? |
| 10:37 | <domfarolino> | annevk: Just blocked on me addressing zcorpan’s last review and making more updates sorry for the huge lag |
| 10:38 | <annevk> | domfarolino: no worries |
| 10:40 | <annevk> | domfarolino: there is some concern with the auto value as it effectively changes the interoperable default to something unknown |
| 10:43 | <annevk> | domfarolino: if we could make progress on this that'd be great though, it seems WebKit is also looking at it again and we're in the early phases of planning |
| 10:43 | <annevk> | domfarolino: so final changes and especially tests would be good to settle on |
| 10:43 | <domfarolino> | annevk: yeah I believe it’s current form allows the UA to do what it wants for auto, I’m guessing this is a deal-breaker? |
| 10:44 | <annevk> | domfarolino: I'm not sure, but it's rather magical and could easily lead to subtle issues |
| 10:46 | <domfarolino> | annevk: I see. also how to spec iframes is unclear. I believe I’ve left some questions somewhere for you on the thread about doing that, but I’ll check. And I’ll update the PR sometime this week. |
| 10:48 | <annevk> | domfarolino: yeah, I wonder if we should tackle <iframe> separately since it's quite a bit different |
| 10:49 | <domfarolino> | Kinda what I’m thinking too |
| 13:53 | <Domenic> | For what it's worth Edge/IE lazy-loaded <img>s for a long time with no interop issues so IMO auto should be OK as a default. Before Edge died it was effectively already the default. |
| 13:54 | <gsnedders> | Quite what was their behaviour? Presto had lots of issues with this from scripts assuming img.onload would fire prior to document.onload or whatever |
| 13:55 | <Domenic> | Yeah unsure what they did with load events, but you could see it in the network panel/server, below the fold images would not get downloaded. |
| 13:56 | <gsnedders> | Like there's definitely subtle behaviour needed here for web compat |
| 13:57 | <annevk> | Yeah, load events is kinda the crucial issue here |
| 13:57 | <gsnedders> | And I think some Masonary-like layout things were using .width and .height to change layout after img.load? |
| 13:58 | <gsnedders> | which is why the Chrome lazyload stuff fetches the initial however many bytes of the image to get the size metadata |
| 14:11 | <annevk> | gsnedders: that's also not defined |
| 14:31 | <domfarolino> | gsnedders: Chrome doesn’t do that anymore |
| 14:31 | <domfarolino> | at least the change has been made to not do that anymore, not sure if it has shipped yet. |
| 14:33 | <annevk> | \o/ |
| 14:42 | <gsnedders> | domfarolino: oh, okay, surprised it didn't break enough from Presto experiences! |
| 14:43 | <domfarolino> | gsnedders: Well Chrome also doesn’t auto-lazyload (unless you’re on Lite mode/data-saver or whatever it’s called, I think on mobile) so that probably helps |
| 14:55 | <gsnedders> | domfarolino: but there was plan to roll it out more generally |
| 15:01 | <domfarolino> | gsnedders: I believe so yeah, but I think that is somewhat contingent on on how rolling it out in Lite mode goes too |
| 16:13 | <jenny-m> | gsnedders: any chance you can provide feedback on https://github.com/web-platform-tests/wpt/issues/19836? |
| 16:17 | <gsnedders> | jenny-m: I definitely didn't start writing one earlier :) |