00:09 | <Domenic> |
|
00:10 | <Domenic> | I didn't realize we had that statement about Navigator in the spec. That's a bit unfortunate in my opinion. |
00:11 | <Domenic> | What is the right action for the participant agreement check in https://github.com/whatwg/html/pull/10547 ? canadahonk was Mozilla employee when he authored it, but is not anymore. |
02:09 | <sideshowbarker> | annevk: FYI https://github.com/web-platform-tests/wpt/issues/49249 |
10:59 | <annevk> | Domenic: pushManager is not established precedent just yet (it's only on ServiceWorkerRegistration to date). I can move it to Window for Declarative Web Push. |
11:04 | <annevk> | sideshowbarker: commented. Test seems correct, albeit confusing and not necessarily testing the intended thing. Although I guess it hit something in Ladybird / Chromium... |
12:21 | <freddy> | Domenic: What is my hope for https://github.com/whatwg/html/issues/8013 seeing some updates? :) |
14:41 | <Shannon Booth> | Hello! I have been trying to debug an issue in Ladybird's implementation of https://github.com/web-platform-tests/wpt/blob/master/url/data-uri-fragment.html The issue in Ladybirds implementation is that the script is running But "try to scroll the fragment" won't guarantee that the target element is set before that script can be run. And if I am understanding navigables right, it wouldn't be a navigation to a fragment either which does have "scroll to the fragment" in it. Would anyone be able to point me to the right direction of how the spec achieves updating the target element before the script is able to query it? |
14:48 | <Shannon Booth> | There look to be some steps which delay the load event for certain stylesheets, but I couldn't spot any criteria which would be relevant there |
23:55 | <Kayla Beezy> | I need help deleting some storage space off my disk |