01:27
<bakkot>
random q: in step 3.1 of Formatter in the console spec, it calls String(arg): https://console.spec.whatwg.org/#formatter
01:28
<bakkot>
this implies to me that console.log(">%s<", ({ toString: () => { return 'custom' } })) should print >custom<, which it does in FF, but not in Chrome (which instead prints >Object<)
01:28
<bakkot>
am I misreading, or is Chrome not following the spec?
10:56
<Luca Casonato>

Could someone explain why running the below snippet on https://google.com results in different output than https://source.chromium.org/? As far as I can tell neither are in quirks mode.

const target = new EventTarget()
target.addEventListener("f", () => {
    console.log("f");
    queueMicrotask(() => console.log("f mt"));
});
target.addEventListener("x", () => {
    console.log("x");
    queueMicrotask(() => console.log("x mt"));
});
target.dispatchEvent(new Event("f"));
target.dispatchEvent(new Event("x"));
10:56
<Luca Casonato>

google.com logs

f
x
f mt
x mt

while source.chromium.org logs

f
f mt
x
x mt
11:00
<Luca Casonato>
Oh, source.chromium.org has a custom queueMicrotask. Should have looked for that right away. Please ignore :-)
12:06
<freddy>
this is why I test on example.com (.net, .org) :P
15:12
<smaug>
anyone recalls why getElementsByTagName and such didn't end up to ShadowRoot?
15:12
<smaug>
ah, I guess because of HTMLCollection
18:15
<sideshowbarker>
https://stackoverflow.com/questions/68742660/when-response-text-promise-will-reject
19:29
<travisleithead>
👋
19:31
<Seirdy>
hey
19:31
<Seirdy>
just copying a question from irc:
19:31
<Seirdy>
question about the navigate-to csp directive (https://w3c.github.io/webappsec-csp/#directive-navigate-to): if i understand it correctly, this doesn't restrict links the user can click on to navigate; it only restricts navigations initiated by JS, redirects, and forms. is this accurate, or is its scope broader?
19:40
<Seirdy>
also: w3.org directed me to irc.w3.org and #whatwg on fleenode. irc.w3.org is mostly empty. freenode -> libera happened, and i was directed from irc to matrix here. so...are questions about w3c specs welcome here, or is there a better place?
19:47
<jgraham>

Seirdy: W3C is theoretically mostly still on IRC, although it's fragmented a bit. You can bridge from matrix to the IRC server if you want to have a single interface.

I think the answer to "are questions about W3C specs welcome here" is "it depends on the spec".

19:47
<jgraham>
I think there are some people who can answer webappsec questions, and I don't know of a better place.
19:51
<Seirdy>

Seirdy: W3C is theoretically mostly still on IRC, although it's fragmented a bit. You can bridge from matrix to the IRC server if you want to have a single interface.

I think the answer to "are questions about W3C specs welcome here" is "it depends on the spec".

the biggest room on irc.w3.org has three members. the second biggest has two members.
19:51
<Seirdy>
i generally prefer using weechat anyway
19:53
<jgraham>
Seirdy: I"m in #w3c#webdriver:matrix.org and there are definitely more than 3 members
19:53
<Alan Stearns>
#css currently has 116 people
19:53
<Seirdy>
wait what
19:54
<Seirdy>
oh wait my usercount script us messed up
19:54
<Seirdy>
nevermind
19:54
<Seirdy>
kids, don't code while sleep deprived or you'll end up like me
19:57
<Seirdy>
ok thanks guys, cya.