Bug 43956 - Pages that use Geolocation should be able to use the page cache
Summary: Pages that use Geolocation should be able to use the page cache
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 40373
Blocks:
  Show dependency tree / graph
 
Reported: 2010-08-13 01:36 PDT by Steve Block
Modified: 2012-03-06 17:31 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Block 2010-08-13 01:36:57 PDT 
Currently, pages that use Geolocation are explicitly prevented from entering the page cache.

When a page enters the page cache, the Frame object is disconnected from the DOMWindow and other objects. In order for Geolocation to work with the page cache, we need to reconnect the Frame to the Geolocation object once the page is restored from the page cache. This will likely require refactoring of Geolocation.

Refactoring is currently blocked by the need to unify all platforms to use a single Geolocation implementation. See Bug 40373.
Comment 1 Steve Block 2010-08-13 01:50:26 PDT 
See Bug 39879 for discussion about Geolocation and the page cache.