Bug 51814
| Summary: | GeolocationPositionCache should not start background thread until a Geolocation method is called | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Steve Block <steveblock> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | jorlow, steveblock |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 51818 | ||
| Bug Blocks: | |||
Steve Block
Currently, we start the DB thread as soon as navigator.geolocation is accessed. Then when a Geolocation method is called, we potentially use a cached position if one is available, but we don't wait for the cache.
We should change this to avoid starting up the background thread when navigator.geolocation is accessed, but its methods are not called.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jeremy Orlow
>> This
>> seems silly since people often fetch the geolocation object in feature
>> detection, even if they are not using it.
>
> Really, do you think it's likely that people feature detect for a feature they don't plan to use?
Yes, libraries do this all the time. I should have caught this in the original review. Please prioritize fixing this.
Steve Block
GeolocationPositionCache was removed in Bug 65289