07:54
<hsivonen>
FYI regarding earlier discussion: https://github.com/orgs/mdn/discussions/242#discussioncomment-4274011 (TL;DR: MDN continuing to use Prettier without forking it.)
08:07
<annevk>

The google style guides are almost an antithesis of what we are teaching at MDN.

o_O

09:25
<sideshowbarker>
https://stackoverflow.com/questions/74638920/iframe-issue-javascript-alert-dialog-block-from-parent-when-added-permissions-p
09:29
<sideshowbarker>

https://stackoverflow.com/questions/74630989/why-use-domstringlist-rather-than-an-array is probably worth an answer from somebody familiar with DOMStringList — and answer with details on its history (from somebody familiar with its history)

I don’t know enough to answer well there. I guess DOMStringList started out as something used in window.location… for some reason, and then it got used with IndexedDB… for some reason — but then not used anywhere else, and won’t be, because sequence<DOMString> is the thing to use instead?

11:28
<Domenic>
Answered. That was a fun one.
11:34
<sideshowbarker>
Answered. That was a fun one.
wow yeah, really great answer — thanks much
11:41
<sideshowbarker>

By the way, https://w3c.github.io/stackoverflow/ is a dashboard thing I put together recently — for daily review of Stack Overflow Q&As for web-platform features (in part as a way to help get a better understanding of which web-platform features developers are actually using, and what their common pain points are)

It is just a set of links to some tag-based searches. If you mouse over the names of the feature sets like Core and Graphics+typography, it’ll show you which tags it’s searching on. Or else if you just follow the links, the search-results pages all also show which tags the results are for.

11:43
<Domenic>
Oh, fun!
16:41
<dlrobertson>
annevk: re https://github.com/whatwg/fetch/pull/1520#discussion_r1037244005 do you have an example of a case where a internal model is specified?
20:32
<TabAtkins>
annevk: I'm trying to figure out how to say "if a URL's fragment is an ID reference" (rather than a Media Fragment, or one of those SVG fragment functions, or the like). Any opinions on how to phrase this?
20:32
<TabAtkins>
(I just need to carve out those other cases as Explicitly Undefined right now.)
20:35
<TabAtkins>
possibly the answer is to just not do that, and instead just unreservedly attempt to find an element with the given ID, and if it fails, handle the failure generically.
20:36
<TabAtkins>
(context: i'm cleaning up the spec text for https://github.com/w3c/csswg-drafts/issues/3320)
21:01
<annevk>
TabAtkins: perhaps HTML's fragment navigation thingie needs an abstraction, but that's where I'd look
21:02
<TabAtkins>
I'm end-running around the thing, since I need to handle "can't find the ID" the same way as "isn't an ID ref at all" anyway
21:02
<annevk>
https://html.spec.whatwg.org/#the-indicated-part-of-the-document
21:02
<annevk>
dlrobertson: Headers/Response/Request all do it pretty well I think
21:03
<dlrobertson>
👍️ thanks I'll take a look
21:03
<annevk>
(really most WHATWG documents are good at separating private from public API)
21:07
<TabAtkins>
annevk: Hm, the "find a potential indicated element" is what I'm reproducing manually right now, so it would be nice to use it, but the algo specifies its "root" argument as a Document, not Document or ShadowRoot
21:08
<TabAtkins>
Well, I'm not doing the a-name resolution, but I could take or leave that
21:14
<annevk>
It should be possible to generalize to allow for another caller (while at the same time maybe constraining the name attribute stuff)
21:14
<annevk>
Gotta go for the day
21:14
<TabAtkins>
kk, i'll raise an issue. thanks for the help!