RESOLVED INVALID 48390
WebKit2 geolocation permission request
https://bugs.webkit.org/show_bug.cgi?id=48390
Summary WebKit2 geolocation permission request
Luiz Agostini
Reported 2010-10-26 17:25:42 PDT
Geolocation permission requests must be sent to the UIProcess to be submitted to the user.
Attachments
patch (14.69 KB, patch)
2010-10-26 17:58 PDT, Luiz Agostini
sam: review-
Luiz Agostini
Comment 1 2010-10-26 17:58:01 PDT
Luiz Agostini
Comment 2 2010-10-29 09:46:45 PDT
ping review
WebKit Review Bot
Comment 3 2010-11-01 08:16:22 PDT
Kenneth Rohde Christiansen
Comment 4 2010-11-11 00:56:54 PST
Comment on attachment 71971 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=71971&action=review > WebCore/page/Geolocation.cpp:216 > +static uint64_t generateId() it seems more to be incrementing an id than really generating one. But maybe that is ok. > WebKit2/UIProcess/WebPageProxy.cpp:1246 > + process()->connection()->send(Messages::WebProcess::SetGelocationPermission(requestID, result), 0); shouldn't this just be send( and not process()->connection()->send ? That should work on trunk > WebKit2/UIProcess/WebPageProxy.h:301 > + // Geolocation permission dot at the end of comments > WebKit2/UIProcess/WebPageProxy.messages.in:104 > + # Geolocation permissions here as well > WebKit2/WebProcess/WebCoreSupport/WebChromeClient.cpp:472 > + WebFrame* webFrame = static_cast<WebFrameLoaderClient*>(frame->loader()->client())->webFrame(); extra space infront of the statuc cast, remove > WebKit2/WebProcess/WebProcess.h:87 > + void setGelocationPermission(uint64_t, bool); Spelling error here! Gelocation, it is called Geolocation > WebKit2/WebProcess/WebProcess.messages.in:46 > + # Geolocation permissions dot at end of comments
Sam Weinig
Comment 5 2010-11-22 14:18:53 PST
Comment on attachment 71971 [details] patch Thus far we have gotten away without adding IDs to WebCore objects and I would like to try and keep it that way. We should instead use an external hash table.
Note You need to log in before you can comment on or make changes to this bug.