Bug 43956
| Summary: | Pages that use Geolocation should be able to use the page cache | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Steve Block <steveblock> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ap, steveblock, tonikitoo |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 40373 | ||
| Bug Blocks: | |||
Steve Block
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Steve Block
See Bug 39879 for discussion about Geolocation and the page cache.