| 06:40 | <annevk> | Domenic: saber1: I think what is missing there is that what’s in the spec doesn’t meet the requirements either. So to play that game we’d remove this from the spec and thrn find agreement on what to add back, no? |
| 15:34 | <Domenic> | What'd we remove? All of dialog? I've been advocating that for some time. |
| 15:43 | <domfarolino> | Huh, I just realized that the domintro title boxes are not searchable I think bc of css ::before https://usercontent.irccloud-cdn.com/file/UNoTGbLt/Screen%20Shot%202020-12-05%20at%2010.41.58.png |
| 15:47 | <domfarolino> | History question: The history handling behaviors #hh-entry-update and #hh-reload are handled by the same spec code in #update-the-session-history-with-the-new-page. However the former says we navigate to an existing entry but replace it's document, and the latter says we should replace the "current session history entry" altogether. Is this inconsistent? |
| 17:22 | <Domenic> | domfarolino: yeah, although the descriptions under the <dfn> for each of them is informal, it's still normative text, so it's wrong. It'd be good to unify them somehow |
| 17:23 | <Domenic> | But first we fix the spec text, then we backport that to the descriptions under the <dfn> |
| 17:59 | <croraf> | Hi. I'm checking a behavior of image "src" replacing. |
| 18:01 | <croraf> | When I have an image loaded, and I replace its "src" attribute, the image stays loaded for some time, until the new image gets loaded from the network. Can this behavior be somehow modified, as in many cases it is not wanted. |
| 18:02 | <croraf> | Chrome waits for the new src to get fully loaded, and then replaces the image at once |
| 23:38 | <domfarolino> | Domenic: Thanks, I filed https://github.com/whatwg/html/issues/6197 for my "full" analysis |
| 23:38 | <domfarolino> | croraf: What is the unwanted behavior. Keeping the old image around for awhile? |
| 23:39 | <croraf> | yes |
| 23:39 | <croraf> | domfarolino, |
| 23:48 | <domfarolino> | croraf: I vaguely remember setting the src to empty string should remove the picture I believe after a queued microtask. So if you src=“”;src=“something” I don’t think that will do what you want. But if you separated the two src mutations by e.g., a setTimeout(... 0) that should work? Sorry not in front of my computer now to test |
| 23:49 | <domfarolino> | croraf: I should also say that our interoperability is OK but not great around image attribute mutations. Chrome adheres pretty well these days though. |
