Closed Bug 314391 Opened 19 years ago Closed 19 years ago

Installing 1.7.12 Does Not Change Build Identifier or "Help/About Mozilla" Info

Categories

(SeaMonkey :: General, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 258158

People

(Reporter: curiousjbh, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.11) Gecko/20050728 Mnenhy/0.7.2.0 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.11) Gecko/20050728 Mnenhy/0.7.2.0 Installing version 1.7.12 does not change Mozilla's version number as far as Mozilla is concerned. I have done it three times and Mozilla is still telling me that it is 1.7.11. Reproducible: Always Steps to Reproduce: 1. Install Mozilla 1.7.12 using auto-installer. Actual Results: Mozilla's Build Identifier on this page says "Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.11) Gecko/20050728 Mnenhy/0.7.2.0". "Help/About Mozilla" takes me to a page with a big, clickable "Mozilla 1.7.11" and underneath that is "Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.11) Gecko/20050728 Mnenhy/0.7.2.0" Could this be a bug in the mnenhy extension? and shouldn't mnenhy be uninstalled anyway, when upgrading to 1.7.12 (I always install extensions to the application directory, not my profile, given a choice ... I *want* to have to reinstall all my extensions after each upgrade.) Expected Results: Mozilla's Build Identifier on this page should say "Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.12) Gecko/????????"; No mention of Mnenhy. "Help/About Mozilla" should take me to a page with a big, clickable "Mozilla 1.7.12" and underneath that should be "Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.12) Gecko/????????"; No mention of Mnenhy" It should be noted that the "Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.11) Gecko/20050728 Mnenhy/0.7.2.0" matches the "about:config" value in Preference name "general.useragent.override", while Preference name "general.useragent.vendorSub" has the value " StumbleUpon/1.999" (note the blank space before the name of the extension)
yeah... in 1.7.x, the version number is extracted from the useragent, and that is overridden by general.useragent.override. if you unset that pref, the display should be correct. later versions use a different mechanism. *** This bug has been marked as a duplicate of 258158 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.