06:33 | <Noam Rosenthal> | Dominic Farolino: right, it results in a network error |
11:19 | <sideshowbarker> | In the WPT test at https://github.com/web-platform-tests/wpt/blob/db6e5032915eb0dcb1d8b8b249488055378245fd/html/webappapis/dynamic-markup-insertion/opening-the-input-stream/url.window.js#L28, what exactly about childDoc causes it to be not fully active at that point? |
11:21 | <sideshowbarker> | I mean in terms of the spec requirements at https://html.spec.whatwg.org/multipage/document-sequences.html#fully-active:
|
11:23 | <sideshowbarker> | …so childDoc must either (a) not be the active document of a navigable, or (b) the navigable is not a top-level traversable, or (c) the navigable’s container document is not fully active. |
11:45 | <annevk> | sideshowbarker: it's a reference to frameURL's document but at that point the nested document is /common/blank.html 's document |
12:10 | <sideshowbarker> | thanks |
15:45 | <Dominic Farolino> | Dominic Farolino: right, it results in a network error |
15:45 | <Dominic Farolino> | My intuition is "no, it wouldn't be blocked" but I'm not 100% confident. |
15:54 | <Noam Rosenthal> | yea CO in CORB stands for cross-origin, but trying to follow how this is done in the fetch spec. |
16:17 | <annevk> | ORB matches that, it should be in the ORB PR. |
18:37 | <Jeffrey Yasskin> | The team working on HTTPS auto-upgrades would like to get https://github.com/whatwg/fetch/pull/1655 into Fetch. What's their next step toward merging it? |
19:51 | <akaster> | Are SVG elements with an id attribute supposed to be exposed as named properties on the window? The section on named properties for the window object says that that should be "HTML Elements" with an id content attribute, which points to a definition that says "elements in the xhtml namespace" |
20:28 | <akaster> | All three major browsers seem to just cache any DOM element with an id attribute, which includes things that aren't what I would think of as HTML elements 🤔 |
20:50 | <Dominic Farolino> | yea CO in CORB stands for cross-origin, but trying to follow how this is done in the fetch spec. |
21:23 | <jarhar> | a friend of mine is asking about how to make use of native context menus on the web, and told me that there was an old now removed thing in firefox which included the menuitem element. are yall aware of any current work or plans to make this kind of thing possible? |
22:50 | <Domenic> | What even is a native context menu? https://www.askvg.com/too-much-inconsistency-in-windows-10-context-menus/ 🤔 |