Skip to content

Commit 6b8f84b

Browse files
[html-events] Add question about load on iframe
1 parent 001ddb0 commit 6b8f84b

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

web-integration/html__events.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,10 @@ When [processing the `iframe` attributes](https://html.spec.whatwg.org/#process-
5050
Firefox fires an unspecified `error` event fired: it should be fired in the same context as the `load` event would.
5151

5252
Note that the captured context is not used for events fired inside the `iframe` as a consequence of the navigation.
53+
54+
> [!NOTE]
55+
> **QUESTION:** Does this actually work? The `load` event is fired for all navigations inside the `iframe`, regardless of how they are triggered (e.g. also if inside the iframe it does `location.href = ...`). Can we distinguish what caused the iframe to navigate when the event is fired?
56+
5357
### 16.3.2 - Frames
5458
When [processing the `frame` attributes](https://html.spec.whatwg.org/#process-the-iframe-attributes), which can happen due to changes to its `src` attribute or due to [it being inserted](https://html.spec.whatwg.org/#frames:html-element-insertion-steps), the user agent must:
5559
- synchronously capture the current AsyncContext, and store it on the `frame` element

0 commit comments

Comments
 (0)