[Webkit-unassigned] [Bug 50513] New: Check If PingLoader Handles Cross Frame Loads Correctly

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=50513

           Summary: Check If PingLoader Handles Cross Frame Loads
                    Correctly
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Page Loading
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: joepeck at webkit.org
                CC: ap at webkit.org, japhet at chromium.org


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?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.