Simplify geolocation permission request in the Content API.

Simplify geolocation permission request in the Content API.

This is the model I used for notifications and will use for other features as they move from RenderView to RenderFrame.

BUG=304341
R=avi@chromium.org, mkosiba@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=277038

[jam, 2014-06-12 21:38:55]

mkosiba: android_webview
avi: the rest

The motivation here is that all these requestpermission calls need to use
WebContents instead of render_process/render_view IDs in the public API. As I
change the code, I'm cleaning things up to use callbacks which allows us to
reduce the API surface. I'm also consolidating permission requests on
ContentBrowserClient, since that's where most of them are already. Lastly, the
"permission context" class is really implementation details of chrome that had
leaked into content.

[Avi (use Gerrit), 2014-06-13 00:36:24]

Non-Android stuff LGTM.

[mkosiba (inactive), 2014-06-13 08:17:03]

Thanks Jam! android_webview LGTM.

https://codereview.chromium.org/330143002/diff/140001/android_webview/browser...
File android_webview/browser/aw_content_browser_client.cc (right):

https://codereview.chromium.org/330143002/diff/140001/android_webview/browser...
android_webview/browser/aw_content_browser_client.cc:403: << "permission
request.";
do we need to result_callback.Run(false); in this case?

[jam, 2014-06-13 14:56:08]

https://codereview.chromium.org/330143002/diff/140001/android_webview/browser...
File android_webview/browser/aw_content_browser_client.cc (right):

https://codereview.chromium.org/330143002/diff/140001/android_webview/browser...
android_webview/browser/aw_content_browser_client.cc:403: << "permission
request.";
On 2014/06/13 08:17:03, mkosiba wrote:
> do we need to result_callback.Run(false); in this case?

Done.