datareporting.healthreport.service.enabled
Continuing from: https://support.mozilla.org/he/questions/954790?esab=a&s=&r=3&as=s
After reading the file http://dxr.mozilla.org/mozilla-central/services/healthreport/README.rst I created in about:config a new Boolean “datareporting.healthreport.service.enabled” (false) and then manually deleted other “datareporting” entries from prefs.js. Most of the entries haven’t reapeared. 2 have: user_pref("datareporting.healthreport.nextDataSubmissionTime", "1365184210363"); user_pref("datareporting.policy.firstRunTime", "1365097810363");
If you can think of a better way please let me know.
Valittu ratkaisu
It appears that the Heath Report is a forthcoming feature that is not yet fully built out. The vision for it was described in this blog post more than six months ago: Firefox Health Report | Blog of Metrics.
I read that the "Nightly" version (and possibly "Aurora") have an about:healthreport screen built in, but this is not available in the released version of Firefox 20 where you see the new preferences in about:config.
I don't think you will see this feature "go live" for a few months. The tracking bug #829887 ("[meta] Beta blockers for Firefox Health Report") shows 9 outstanding bugs that need to be closed before the feature is enabled for beta versions.
When it goes live, based on the current design, a new checkbox will appear in Options/Preferences to turn it on or off, similar to the checkboxes for telemetry and crash reporting. (The attached image is for Firefox 20. See also the about:telemetry page.)
So... I can't imagine that Firefox 20 is sending any actual health data at this point, and certainly not without disclosure, as a huge amount of work has been done behind the scenes on all the details of that. Someone should please confirm that.
Lue tämä vastaus kontekstissaan 👍 1Kaikki vastaukset (19)
Valittu ratkaisu
It appears that the Heath Report is a forthcoming feature that is not yet fully built out. The vision for it was described in this blog post more than six months ago: Firefox Health Report | Blog of Metrics.
I read that the "Nightly" version (and possibly "Aurora") have an about:healthreport screen built in, but this is not available in the released version of Firefox 20 where you see the new preferences in about:config.
I don't think you will see this feature "go live" for a few months. The tracking bug #829887 ("[meta] Beta blockers for Firefox Health Report") shows 9 outstanding bugs that need to be closed before the feature is enabled for beta versions.
When it goes live, based on the current design, a new checkbox will appear in Options/Preferences to turn it on or off, similar to the checkboxes for telemetry and crash reporting. (The attached image is for Firefox 20. See also the about:telemetry page.)
So... I can't imagine that Firefox 20 is sending any actual health data at this point, and certainly not without disclosure, as a huge amount of work has been done behind the scenes on all the details of that. Someone should please confirm that.
Thank you for the detiled explanation. I appreciate it.
I just wanted to get rid of the confusing entries in prefs.js, and it seems to have worked. :)
You may be interested in this Knowledge Base discussion
I took Larissa's initial text (in a private google doc) and drafted the article. I approved it since the feature will be released in beta tomorrow.
Release notes confirm Preliminary implementation of Firefox Health Report (see FAQ) http://www.mozilla.org/en-US/firefox/21.0beta/releasenotes/
Thank you.
The Knowledge Base discussion is indeed interesting. For the time being, is there a better way to completely disable the feature?
I am having difficulty finding out much about this new feature.
I would be interested in seeing it working. Potentially it is a useful troubleshooting tool once implemented.
The article linked from the discussion suggests once implemented sharing of the information may be disabled, whilst still having the information available locally and privately. This will be selectable from within the Ui. See for instance p15 of 28 in http://people.mozilla.com/~lco/FHR/130315%20FHR%20MVP-v1.pdf
This FHR is apparently not yet working for me, although I have no idea whether or not it submits data. It seems rather odd to introduce a feature with minimal warning that submits data by default.
If you do turn it off I wonder if you then get a nag line, as apparently happened in this instance when telemetry was disabled /forums/contributors/709112#post-51789
Interestingly the crash reporting and telemetry options seem to have gone and been replaced with FHR option only !!
(Edit Should at least have telemetry option, probably never had Crash option on this! )
Muokattu
I added the “datareporting.healthreport.service.enabled” entry a few hours ago and the 'nag line' hasn't popped up since. Could you try it and let me know?
I'm using v20 and the 'Data Choices' tab hasn't changed.
Muokattu
As I mentioned above I am having difficulty locating documentation on this feature and the implementation.
I added the “datareporting.healthreport.service.enabled” entry a few hours ago and the 'nag line' hasn't popped up since
I thought your objective may be to prevent data submission /questions/954790. The name of that pref suggests data will be sent.
BiDi
I note in in this forum your locale justifies right, whereas mine is writing left to right and jusifies left.
I set “datareporting.healthreport.service.enabled” to false.
Well, the 'nag line' has returned. I guess I should leave user_pref("datareporting.policy.dataSubmissionPolicyResponseType", "accepted-info-bar-dismissed");
My locale is Hebrew. Do you know how to justify my posts to the left?
Muokattu
My locale is Hebrew. Do you know how to justify my posts to the left?
This site changes the layout depending on the language code in the URL. If you delete the language code and the extra / then the site will detect the viewer's language and redirect. That way, you can post language-neutral URLs. (I rarely remember to do that.)
Thank you jscher2000.
If I paste https://support.mozilla.org/questions/955458#answer-423928 in the urlbar, it redirects me to https://support.mozilla.org/he/questions/955458#answer-423928.
The only way to change the site to LTR is switching Language at the top of the page, and it has to be done for each and every page even on the same session.
I suppose that rather than the site assuming it knows what you want, it would be nice to have a choice... Actually, I just noticed at the very top of the page that I have the word ENGLISH and clicking that lets me choose a different language. LTR and RTL is not the same as language, but I think on this platform, that might be as close as we can get for the moment.
Aha, to address your point about every page, yes, the language is encoded into the links in the page, but if you have to navigate directly, your language is detected again. Not sure why a cookie isn't used...
Muokattu
Thanks again.
Your answers are always enlightening. :)
That you get a RTL Hebrew page is likely caused by the language setting with Hebrew set as the first choice.
- Tools > Options > Content > Languages
I see that the Solved and Contributed check is still at the left side and hardly visible with RTL, looks like a bug with the CSS to me.
Thank you cor-el. I’m impressed!
Can I have an exception to that setting? As it is, all pages that can be displayed in multiple languages (e.g. Facebook) are displayed in English.
You will have to include the wanted language in the link like /en-US/ at this forum or change the order of the languages and place English at the top top to make that the default choice.
Thanks again.
Another option is creating a button toggling the preference.
If I do that, I'll post the code.
Note that intl.accept_languages is a complex pref that can be localized and thus needs special handling.
Components.utils.import("resource://gre/modules/Services.jsm"); var ps = Services.prefs; var pref = "intl.accept_languages"; var value = ps.getComplexValue(pref,Components.interfaces.nsIPrefLocalizedString).data; alert(data);
Thank you. I appreciate your time.
The following code works for me:
function toggleAcceptLanguages()
{
var ps = Cc["@mozilla.org/preferences-service;1"].getService(Ci.nsIPrefBranch); ps.setCharPref("intl.accept_languages", ps.getCharPref( "intl.accept_languages") == "he,he-il,en-us,en" ? "en-us,en,he,he-il" : "he,he-il,en-us,en");
}
Muokattu