>+++ b/suite/locales/en-US/chrome/common/help/cs_nav_prefs_advanced.xhtml Sat May 02 06:00:36 2020 +0100 >@@ -498,18 +498,16 @@ > The identifier sent by &brandShortName; to all websites is used for > statistics about website usage but also sometimes to expose certain features > only to known browsers (a practice known as "sniffing"). Consequently, >- unchecking any of these boxes may result in websites or remote calendar >- services not working properly. >+ changing this option may result in websites or remote calendar >+ services not working properly. &brandShortName; can: Yes, please remove the "or remote calendar services" bit. > <ul> >- <li><strong>Advertise Firefox compatibility</strong>: If this is enabled, >+ <li><strong>Identify as &brandShortName;</strong></li> There should probably be something about what this does even if it is just "&brandShortName; will identify itself soley as &brandShortName; and not contain anything donating compatibility with Firefox." >+ <li><strong>Identify as &brandShortName; and advertise Firefox compatibility</strong>: > &brandShortName; will identify itself as both &brandShortName; and also > compatible with Firefox. This allows websites that check for certain > browsers rather than certain functionality to work with &brandShortName;.</li> >- <li><strong>Advertise Lightning installation</strong>: This option is >- only available when the Lightning calendar extension is installed and >- activated. If this is enabled, &brandShortName; will add information on >- Lightning being installed and which version, thus calendaring websites >- and/or remote calendar services can customize their communication.</li> >+ <li><strong>Identify as Firefox</strong>: Do not mention >+ &brandShortName;, send a Firefox identifier instead.</li> These should be in the same order as in the preferences, so this should be first in the list. Also probably need to add something about why this option might be suitable in certain circumstances. f+ for the moment as I would like to see the next iteration of the patch. Thanks for the work so far.
Bug 1242294 Comment 55 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
>+++ b/suite/locales/en-US/chrome/common/help/cs_nav_prefs_advanced.xhtml Sat May 02 06:00:36 2020 +0100 >@@ -498,18 +498,16 @@ > The identifier sent by &brandShortName; to all websites is used for > statistics about website usage but also sometimes to expose certain features > only to known browsers (a practice known as "sniffing"). Consequently, >- unchecking any of these boxes may result in websites or remote calendar >- services not working properly. >+ changing this option may result in websites or remote calendar >+ services not working properly. &brandShortName; can: Yes, please remove the "or remote calendar services" bit. > <ul> >- <li><strong>Advertise Firefox compatibility</strong>: If this is enabled, >+ <li><strong>Identify as &brandShortName;</strong></li> There should probably be something about what this does even if it is just "&brandShortName; will identify itself soley as &brandShortName; and not contain anything indicating compatibility with Firefox." >+ <li><strong>Identify as &brandShortName; and advertise Firefox compatibility</strong>: > &brandShortName; will identify itself as both &brandShortName; and also > compatible with Firefox. This allows websites that check for certain > browsers rather than certain functionality to work with &brandShortName;.</li> >- <li><strong>Advertise Lightning installation</strong>: This option is >- only available when the Lightning calendar extension is installed and >- activated. If this is enabled, &brandShortName; will add information on >- Lightning being installed and which version, thus calendaring websites >- and/or remote calendar services can customize their communication.</li> >+ <li><strong>Identify as Firefox</strong>: Do not mention >+ &brandShortName;, send a Firefox identifier instead.</li> These should be in the same order as in the preferences, so this should be first in the list. Also probably need to add something about why this option might be suitable in certain circumstances. f+ for the moment as I would like to see the next iteration of the patch. Thanks for the work so far.