WHATWG on 2022-06-03

07:21	<annevk>	Luca Casonato: heya, https://common-min-api.proposal.wintercg.org/ doesn't list `ErrorEvent`, do you know if Deno or Node.js would be impacted by changes to it?
07:56	<Luca Casonato>	Luca Casonato: heya, https://common-min-api.proposal.wintercg.org/ doesn't list `ErrorEvent`, do you know if Deno or Node.js would be impacted by changes to it? Deno would. We have WebSocket, which uses it.
07:57	<Luca Casonato>	Good catch btw!
08:10	<annevk>	Yoav Weiss: crbug.com/new is failing. Is that going to be fixed?
08:16	<Yoav Weiss>	Thanks for letting me know!
08:16	<Yoav Weiss>	I'll bug folks that actually know how that infra works
08:38	<Yoav Weiss>	crbug.new seems to be working
08:58	<Noam Rosenthal>	Noam Rosenthal: why don't we if that's what gets painted? It is a heuristic to make higher quality images count as larger than upscaled ones. that metric can be gamed in so many other ways though IMO. Yoav Weiss probably has more context on LCP than myself ☺️
09:05	<Noam Rosenthal>	It is a heuristic to make higher quality images count as larger than upscaled ones. that metric can be gamed in so many other ways though IMO. Yoav Weiss probably has more context on LCP than myself ☺️ Think of the placeholder use case, when an image element shows a low-quality upscaled image and then loads the full-res image later. The full-res image would be considered larger for purposes of LCP than the placeholder
09:13	<sideshowbarker>	Yoav Weiss: looking at https://www.w3.org/TR/largest-contentful-paint/ I see it still shows https://wicg.github.io/largest-contentful-paint as the ED URL — where instead it should be https://w3c.github.io/largest-contentful-paint/ (which the wicg URL redirects to). Should I go ahead and raise a PR with a patch?
09:14	<sideshowbarker>	hmm I see the source at https://github.com/w3c/largest-contentful-paint/blob/4a0930ca74a98941237635424cd34c8a44825b2d/index.bs#L10 does already have the w3c URL
09:18	<sideshowbarker>	aha I see https://github.com/w3c/largest-contentful-paint/commit/4a0930ca74a98941237635424cd34c8a44825b2d from 4 days ago already fixed it. Can you re-build and re-publish that to https://www.w3.org/TR/2022/WD-largest-contentful-paint-20220524/ ? It’s currently causing some of the mdn-spec-links automation to fail.
09:25	<Yoav Weiss>	we should really just auto-publish all the things..
09:26	<sideshowbarker>	yes you should :)
09:27	<sideshowbarker>	I could help y’all set it up but if this in the webperf group, I think Xiaoqian could too
12:25	<zcorpan>	smaug: ping https://github.com/whatwg/dom/issues/952
12:27	<zcorpan>	and Sam Sneddon [:gsnedders] (or someone from webkit, cdumez seemingly isn't here) ^
16:09	<Domenic>	Noam Rosenthal: I just noticed there are three response variables in https://html.spec.whatwg.org/#preload , with the outer one in step 8 being shadowed? Can that one be deleted?
16:12	<Noam Rosenthal>	Noam Rosenthal: I just noticed there are three response variables in https://html.spec.whatwg.org/#preload , with the outer one in step 8 being shadowed? Can that one be deleted? Yea, the outer one is a leftover and should be removed since there's a `preload entry`'s `response` instead.
16:12	<Domenic>	Ah great. Feel free to do so in the same refactoring PR, or in a separate one.
16:13	<Noam Rosenthal>	Ah great. Feel free to do so in the same refactoring PR, or in a separate one. Done
19:53	<wanderview>	how do I overload an algorithm name in html spec? I tried the "for=foo" thing in the <dfn> tag, but it didn't seem to work
20:20	<wanderview>	I guess data-x is my friend
21:07	<Domenic>	wanderview: yeah, https://github.com/whatwg/wattsi/blob/main/Syntax.md is the more-or-less full docs, it's not nearly as good as Bikeshed.