User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9pre) Gecko/2008040501 SeaMonkey/2.0a1pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9pre) Gecko/2008040501 SeaMonkey/2.0a1pre The old Navigator name for the browser component still occur here in this file: <http://mxr.mozilla.org/seamonkey/source/suite/locales/en-US/chrome/common/help/using_priv_help.xhtml#1574> Reproducible: Always Steps to Reproduce: 1. Open Help 2. Navigate to Using Privacy Features >> Managing Images >> Image Preferences Actual Results: Reads "Navigator" three times. Expected Results: Should read "the browser" or "SeaMonkey" (&brandshortname;).
http://mxr.mozilla.org/comm-central/source/suite/locales/en-US/chrome/common/help/using_priv_help.xhtml lines 1575, 1579 and 1584 Updating the file location above and letting it block the tracker bug.
hmm, "browser" or &brandShortname; is the question... This pref is not under browser, and the pref text says "SeaMonkey". However, does this pref controls also image prefs in, for instance, mailNews (can't think of anything else it affects)?
(In reply to comment #2) > hmm, "browser" or &brandShortname; is the question... This pref is not under > browser, and the pref text says "SeaMonkey". However, does this pref controls Remove "However"...
either "&brandShortname;" or "the &brandShortname; browser" sounds good to me.
I made some small simplification/re-wordings (no point mentioning "the &brandShortName; browser" more than twice etc).
Attachment #344498 - Flags: review?(iann_bugzilla)
+<p>Image Acceptance preferences allows you to control whether or under what Should be "allow" as Ian pointed out on irc.
Comment on attachment 344498 [details] [diff] [review] Fix references r=me with allows->allow change
Attachment #344498 - Flags: review?(iann_bugzilla) → review+
Pushed changeset 2d18512704e7 to comm-central (with allows --> allow change).
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.0a2
You need to log in before you can comment on or make changes to this bug.