Bug 50513 – Check If PingLoader Handles Cross Frame Loads Correctly

• Status: NEW
• Component: Page Loading

[Joseph Pecoraro]

In a conversation with Alexey, he mentioned we should check if unload image loads
made via cross-frame boundaries inside one frame's unload handler is handled properly.

For example, given a page with an iframe. When that page is unloaded, if the iframe's
unload handler triggers an image load on the top frame (main document) does that
image load get treated properly by becoming a PingLoader. If the
m_pageDismissalEventBeingDispatched state of the iframe is true, can the above
scenario still cause an image to be loaded on another frame and should that
load then have PingLoader privileges or not.

Possible scenarios:

  1) Main document has an iframe, main document navigates, iframe's unload triggers load in parent frame
  2) Main document has an iframe, iframe element is removed, iframe's unload triggers load in parent frame
  3) Main document has an iframe, iframe document navigates, iframe's unload triggers load in parent frame

  • What should happen in these scenarios?
  • Do we handle them sanely?
  • Should we create tests for them?

[Alexey Proskuryakov]

Here are the reasons to improve on this:
- if PingLoader doesn't intercept such request, and it is canceled, then the frame gets into a load error state, and doesn't go into back/forward cache;
- well, make statistics work.