1312804 - Iframe that constantly reloads doesn't prevent parent load event

Status: NEW

(Core :: DOM: Navigation, defect, P3)

Description

[Josh Matthews [:jdm]]

Attachment: Testcase

The spec says that calling location.reload() should put the iframe into "delaying load events" mode. Since this is synchronous, I would expect a page that always reloads itself during the initial parse would mean that the parent document would never be able to dispatch a load event. The attached testcase shows that Firefox happily does so, even though there's never an iframe load event.

Couldn't verify Blink's behaviour, since the testcase made it unresponsive.

Comment 1

[Boris Zbarsky [:bzbarsky]]

> should put the iframe into "delaying load events" mode.

Yes, but when?  You're looking at https://html.spec.whatwg.org/multipage/browsers.html#navigate step 9, right?

That's after the load event has been queued, no?  _That_ happens in step 8 when the previous navigation is aborted...

Comment 2

[Boris Zbarsky [:bzbarsky]]

I guess it depends on exactly what https://html.spec.whatwg.org/multipage/syntax.html#stop-parsing step 6 means.  In particular, what happens if a single task first leads to a state where nothing is blocking, and then to a state where something is blocking.

Comment 3

[Josh Matthews [:jdm]]

Anne, do you have any input here?

Comment 4

[Josh Matthews [:jdm]]

More specifically, is this something I should raise in the whatwg issue tracker?

Comment 5

[Anne (:annevk)]

You should probably raise it. The main questions I'd have is what the various browsers end up doing here, what is most desired, and how we are constrained by the web.