[Webkit-unassigned] [Bug 55577] New: Geolocation should continue to work after iframe reparenting

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Mar 2 07:47:05 PST 2011


           Summary: Geolocation should continue to work after iframe
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jknotten at chromium.org

In https://bugs.webkit.org/show_bug.cgi?id=52877, dimich writes

"When we transfer iframe, the main idea of the feature is that it continues all operations. If it is being loaded - it continues to load, if it has timers or XHRs in flight - they continue to work. Basically, since the iframe has its own origin, the security checks and permissions of various kind can continue to be checked against that origin. It would be unfortunate if the geolocation will stop working when iframe is transferred. It would be nice to figure out how to make it work, unless it contradicts the was Geolocation permissions are granted."

In bug 52877, we stop the activities of the Geolocation when the iframe is transferred between pages because the old page client is becoming inaccessible, and we won't otherwise be able to stop activities when the old page client is destroyed. Also, it may be that the permission policy is different under the new client.

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

More information about the webkit-unassigned mailing list