However it is concerning to have code in an Open source project that is
1.Mostly undocumented
2.Could be confusing to privacy-aware users
3.Harvests data without proper privacy notices
4.Has been added prematurely without proper documentation and serves no purpose like say, dom.webcomponents.enabled , does in making the browser more standards-compliant or up to date with an early W3C Specification
In my opinion this sort of feature should be held back from any mainstream release until it is clear to the end user exactly what it does. You appear to still not have a real focus for it from your messages which I find very worrying. I find that clear documentation is important and my only gripe with alot of products right now.
04.04.2016, 19:30, "Mark Banner" <mban...@mozilla.com>:
On 04/04/2016 16:49, a...@imgland.xyz wrote:I don't know much about Mozilla's privacy but in my opinion feel the
need to immediately remove it from Firefox and push a new beta build
I can understand your concern, however, please understand that this
logging functionality is currently disabled by default - see the
"loop.logDomains" preference.
We won't be enabling it until the privacy review is completed.
If you wish to inspect and validate my assertion, you are quite welcome to.
Here's a link to the code so that you can see what is currently on beta
http://mxr.mozilla.org/mozilla-beta/search?string=loop.logDomains&find=&findi=&filter=%5E%5B%5E%5C0%5D*%24&hitlimit=&tree=mozilla-beta
You can also see from the test file there, that we have a test to check
that nothing is logged if the pref is set to false.
Mark.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
