Closed
Bug 271517
Opened 20 years ago
Closed 20 years ago
Security update from 0.9.3 does not suggest 1.0
Categories
(www.mozilla.org :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: samuel, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Build Identifier: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 The uppdate page for people using 0.9.3 suggests update to 0.10, and does not menti0n the (now current) 1.0 I understand that <i>some</i> people might want to stay at 0.10 for compatability reasons, but I expect that the vast majority would be better served by having 1.0 (or whatever the current production version is) suggested to them. Reproducible: Always Steps to Reproduce: 1. start a 0.9.3 browser with the default start page. 2. 3. Actual Results: Suggest upgrading to 0.10 Expected Results: Should suggest upgrading to current version. (and possibly offer 0.10 as a deprecated option)
urgh: the page says 0.10 but it does direct you to a page which feeds you 1.0. its really just a cosmetic error.
Severity: normal → trivial
strong related is Bug 271283
Component: Software Update → Web Site
QA Contact: bugs
Comment 3•20 years ago
|
||
Moving to "Software Update" ("website" is for problems with
http://www.mozilla.org/products/firefox/)Component: Web Site → Software Update
Comment 4•20 years ago
|
||
It was the latest version of Firefox when the press release was out. They are not going to update product's versions on all their pages each time a new version is out.
Assignee: bugs → mozilla.webmaster
Component: Software Update → webmaster@mozilla.org
Product: Firefox → mozilla.org
QA Contact: danielwang
Version: unspecified → other
Updated•20 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•16 years ago
|
Product: mozilla.org → Websites
Updated•12 years ago
|
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•