Closed
Bug 491653
Opened 16 years ago
Closed 16 years ago
geo.enabled should be listed in about:config by default and not be a hidden setting
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: stevee, Assigned: johnath)
Details
(Keywords: verified1.9.1, Whiteboard: [geo])
Attachments
(1 file, 1 obsolete file)
772 bytes,
patch
|
johnath
:
review+
|
Details | Diff | Splinter Review |
Currently to disable the geolocation in firefox you have to set geo.enabled to false in about:config. This setting is not present by default but a 'hidden' pref that you have to add manually.
geo.enabled should be listed in about:config by default so it's more obvious as to how to turn this feature off if desired.
Flags: blocking-firefox3.5?
Reporter | ||
Updated•16 years ago
|
Summary: geo.enabled should be in about:config and not a hidden setting → geo.enabled should be listed in about:config and not be a hidden setting
Reporter | ||
Updated•16 years ago
|
Summary: geo.enabled should be listed in about:config and not be a hidden setting → geo.enabled should be listed in about:config by default and not be a hidden setting
Comment 1•16 years ago
|
||
The default setting should be false to disable geolocation for safety and security reasons.
![]() |
Assignee | |
Comment 2•16 years ago
|
||
Updated•16 years ago
|
Attachment #376057 -
Flags: review?(gavin.sharp) → review+
Comment 3•16 years ago
|
||
Comment on attachment 376057 [details] [diff] [review]
Add the pref with a default of true
a191=beltzner
Attachment #376057 -
Flags: approval1.9.1+
Comment 4•16 years ago
|
||
(In reply to comment #2)
> Created an attachment (id=376057) [details]
> Add the pref with a default of true
Shouldn't a feature with user privacy and security concerns default to disabled or false?
See this forum thread for spirited discussion of the issue.
http://forums.mozillazine.org/viewtopic.php?f=23&t=1226785
![]() |
Assignee | |
Comment 5•16 years ago
|
||
(In reply to comment #4)
> (In reply to comment #2)
> > Created an attachment (id=376057) [details] [details]
> > Add the pref with a default of true
>
> Shouldn't a feature with user privacy and security concerns default to disabled
> or false?
>
> See this forum thread for spirited discussion of the issue.
>
> http://forums.mozillazine.org/viewtopic.php?f=23&t=1226785
I'm acquainted with the discussion there, but I also haven't seen issues raised there which are particularly realistic or balanced (no offense intended if you are a participant in those discussions). This feature doesn't send any information without express confirmation, it uses a non-modal notification bar with clear choices, allows users to ignore the notification bar or browse to a different site, and moreover, the work in this patch makes the pref to disable it incrementally MORE visible.
Beyond all that, though, debates about the global behaviour of a new content feature don't really belong in bugs, they belong in newsgroups. I'd suggest mozilla.dev.platform, though again, I'd encourage anyone doing so to have more salient concerns than those expressed in the thread you reference. The conversation there is toxic and inflammatory, and seems to ignore the fact that this is a per-site, per-interaction, opt-in feature unless you explicitly instruct us otherwise.
This bug is concerned exclusively with making the existing behaviour more visible and easier to change. I appreciate your advocacy, I am extremely interested in web privacy issues myself, but I hope you'll agree that this bug isn't really the place for it.
![]() |
Assignee | |
Comment 6•16 years ago
|
||
Gavin suggests moving to all.js - same code, I'm guessing his review carries
Attachment #376057 -
Attachment is obsolete: true
Attachment #376069 -
Flags: review+
![]() |
Assignee | |
Comment 7•16 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 8•16 years ago
|
||
Adding QA Contact for geolocation related bugs (geolocation@core.bugs) to CC list, since this bug is directly related with it.
(In reply to comment #0)
> Currently to disable the geolocation in firefox you have to set geo.enabled to
> false in about:config. (...)
It is worth mentioning that this pref is obeyed only after restart of the browser after making a change. This is bug 491766.
(In reply to comment #4)
(...)
>
> See this forum thread for spirited discussion of the issue.
>
> http://forums.mozillazine.org/viewtopic.php?f=23&t=1226785
And http://www.robotfromthefuture.com/2009/05/i-have-a-problem-with-geolocation/ (with comments)...
(In reply to comment #7)
> http://hg.mozilla.org/mozilla-central/rev/5e2c0a5512f4
Why only mozilla-central? This means this fix will not be available in FF3.5. I don't think that this is the desired outcome, the pref shouldn't be hidden in FF3.5.
Comment 9•16 years ago
|
||
Keywords: fixed1.9.1
Whiteboard: [geo]
Reporter | ||
Comment 10•16 years ago
|
||
Clearing blocking 3.5 request since this has just landed.
Flags: blocking-firefox3.5?
Comment 11•16 years ago
|
||
(In reply to comment #8)
> Why only mozilla-central? This means this fix will not be available in FF3.5. I
> don't think that this is the desired outcome, the pref shouldn't be hidden in
> FF3.5.
Patches must land on mozilla-central first and "bake" there for a build cycle before landing on 191.
Comment 12•16 years ago
|
||
Verified fixed on the trunk using Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090508 Minefield/3.6a1pre and Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090508 Minefield/3.6a1pre.
Verified fixed on the 1.9.1 branch using and Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b5pre) Gecko/20090508 Shiretoko/3.5b5pre and Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b5pre) Gecko/20090508 Shiretoko/3.5b5pre.
Status: RESOLVED → VERIFIED
Keywords: fixed1.9.1 → verified1.9.1
Comment 13•16 years ago
|
||
(In reply to comment #8)
(...)
> And
> http://www.robotfromthefuture.com/2009/05/i-have-a-problem-with-geolocation/
> (with comments)...
For some reason this page is 404 now. Here is a copy in WebCite: http://www.webcitation.org/5gSDGCKAq (there were some comments after May 1st, but unfortunately I don't have a link to a newer version).
You need to log in
before you can comment on or make changes to this bug.
Description
•