[Dev] Mozilla Social
emulatorman at riseup.net
Thu Sep 11 15:04:08 GMT 2014
-----BEGIN PGP SIGNED MESSAGE-----
On 09/11/2014 09:16 AM, André Silva wrote:
> On 09/11/2014 05:08 AM, hellekin wrote:
>> On 09/11/2014 04:08 AM, André Silva wrote:
>>> On 08/28/2014 06:21 AM, André Silva wrote:
>>>> On 08/21/2014 01:00 PM, hellekin wrote:
>>>>> in icedove non-prism there's a configuration that
>>>>> whitelists Mozilla Social for some "nice" services, like,
>>>>> ahem, MSN. See screenshot.
>>>>> == hk
>>>> ok, i will check to fix and build a new revision of it and
>>>> let you know when it's ready
>>> Social API support has been removed on iceweasel
>> *** Social API is OK. What is not OK, is the default using
>>> Otherwise, geolocation backend support has been removed on
>>> icedove  like iceweasel 
>> *** Again, geolocation CAN BE OK, if you know what you're doing.
>> I don't think removing the functionality is good at all. The
>> technology is not bad, its abuse is.
>> *** Instead of removing the Preferences, why not empty them, and
>> for the booleans, put them to false? That way, people can
>> choose to enable them. Otherwise, how does the browser react
>> when it finds empty preferences and a site tries to call that
>> API? It's potentially more complicated than just removing the
>> prefs, and if not now, in later releases. What do you think?
>> *** Ditto. "geo.enable = false" looks safer than nothing at all.
>> Thank you for tackling that issue!
>> == hk
> ok, then i will revert the changes and keep empty them and booleans
> in false, but i prefer put it on vendor.js to keep it more
> practical for us.
I've added the new changes on iceweasel  and icedove  and i'm
building them. I let you know when it be done.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
More information about the Dev