Bug 2037074 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
The current permission story of geolocation is deeply sad:

1. The content process pings the parent process for the initial browser-level permission prompt
2. The parent process pings back
3. If it's granted, the content process pings the parent again for the system-level permission prompt
4. The parent process pings back
5. If it's also granted, the content process pings the parent again for the geolocation request

The ideal way is to:

1. The content process pings the parent process for the geolocation request
2. The parent process figures out the permission story (and opens permission prompt if needed), and ping back with the result
Revision 1 by
on 
The current permission story of geolocation is deeply sad:

1. The content process pings the parent process for the initial browser-level permission prompt
2. The parent process pings back
3. If it's granted, the content process pings the parent again for the system-level permission prompt
4. The parent process pings back
5. If it's also granted, the content process pings the parent again for the geolocation request
6. The parent process pings back with the geolocation data

The ideal way is to:

1. The content process pings the parent process for the geolocation request
2. The parent process figures out the permission story (and opens permission prompt if needed), and ping back with the result
Revision 2 by
on 
The current permission story of geolocation is deeply sad:

1. The content process pings the parent process for the initial browser-level permission prompt
2. The parent process pings back
3. If it's granted, the content process pings the parent again for the system-level permission prompt
4. The parent process pings back
5. If it's also granted, the content process pings the parent again for the geolocation request
6. The parent process pings back with the geolocation data

The ideal way is:

1. The content process pings the parent process for the geolocation request
2. The parent process figures out the permission story (and opens permission prompt if needed), and ping back with the result

Back to Bug 2037074 Comment 0