Bug 70330

Summary: Enable geolocation client based flag for Qt5
Product: WebKit Reporter: Adenilson Cavalcanti Silva <savagobr>
Component: WebKit QtAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: kenneth, webkit.review.bot
Priority: P3    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
use the same geolocation features for Qt5
none
This patch tests for the locatio module. none

Adenilson Cavalcanti Silva
Reported 2011-10-18 08:01:28 PDT
This patch will allow to have geolocation support activated by default.
Attachments
use the same geolocation features for Qt5 (1.56 KB, patch)
2011-10-18 08:13 PDT, Adenilson Cavalcanti Silva 		no flags
DetailsFormatted DiffDiff
This patch tests for the locatio module. (1.63 KB, patch)
2011-10-19 12:59 PDT, Adenilson Cavalcanti Silva 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Adenilson Cavalcanti Silva
Comment 1 2011-10-18 08:13:05 PDT
Created attachment 111446 [details] use the same geolocation features for Qt5 I tested it in Qt5, next I will test on Qt 4.x.
Tor Arne Vestbø
Comment 2 2011-10-18 08:21:16 PDT
Comment on attachment 111446 [details] use the same geolocation features for Qt5 Is there a way you can pick up if someone build Qt5 with -no-location?
Adenilson Cavalcanti Silva
Comment 3 2011-10-18 08:34:41 PDT
I just tested with Qt 4.7.2 and it is working fine. Tor: I'm not aware if is there a flag for it in Qt5. But -location is turned on by default.
Adenilson Cavalcanti Silva
Comment 4 2011-10-19 12:59:29 PDT
Created attachment 111661 [details] This patch tests for the locatio module.
WebKit Review Bot
Comment 5 2011-10-20 03:21:26 PDT
Comment on attachment 111661 [details] This patch tests for the locatio module. Clearing flags on attachment: 111661 Committed r97956: <http://trac.webkit.org/changeset/97956>
WebKit Review Bot
Comment 6 2011-10-20 03:21:31 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.