[Webkit-unassigned] [Bug 40162] Prevent Geolocation making callbacks to a ScriptExecutionContext that no longer exists

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jun 9 02:06:49 PDT 2010


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





--- Comment #16 from Jeremy Orlow <jorlow at chromium.org>  2010-06-09 02:06:47 PST ---
(In reply to comment #15)
> My idea is:
> - Geolocation can be a tiny object that implements the API (similar to Navigator);
> - it won't be "active" in any way;
> - whenever a request for position is made (either one shot or repeating), an object to handle this request is created. In fact, it will be similar to DOMTimer even more than to XMLHttpRequest;
> - these request objects are ActiveDOMObjects. Like DOMTimers, they are not directly exposed to JS;
> - I'm not really sure who should track granted permissions. Logically, it sounds like this is a job for SecurityOrigin.
> 
> Does this make sense? I think that the similarity to DOMTimer is very close - even down to watchers being represented as long IDs, like timers created with setInterval() are.

This seems like a very reasonable design, but what are the upsides of adding the extra layer to the design?

-- 
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