Closed
Bug 296789
Opened 20 years ago
Closed 19 years ago
Stop 1.0.x users trying to install 1.0+-only addons
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
1.0
People
(Reporter: mozilla, Assigned: csthomas)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050531 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050531 Firefox/1.0+ Lots of users think "1.0+" means 1.0.4 and aren't happy when extensions compatible only with "1.0+" won't install on 1.0.4, the newest release. A note should be added to the front page explaining that "1.0+" refers to developers' builds of Firefox and not to 1.0.x releases. On the plus side, the fact that "dumb users" know 1.0.4 is the latest release is a testament to MoFo's anti-marketing of 1.1a1. Reproducible: Always Steps to Reproduce: 1. Be a dumb user 2. Try to install an extension for "Firefox 1.0+ - 1.0+" Actual Results: Won't install, user cries Expected Results: Won't install, user doesn't cry because user knows that 1.0+ != 1.0.x. Afterthought: an alternative solution (possibly better) would be to change the display of "1.0+" to "1.0+ (developers' versions only)" or similar.
Comment 1•19 years ago
|
||
Better (I thought was already implemented) solution - by default, hide extensions that have a higher minVersion value than the version in the current client's user agent. This needs a higher priority, for the people that try to install extensions, this is, at best, a major bug. I suggest that the priority gets bumped and this is taken care of before Deer Park Alpha 2 if possible.
Browser detection doesn't seem to be our forte. Unfortunately, the GUI provides no method to filter either. But that's a different bug. Reassigning to CTho to get a little traction on this.
Assignee: Bugzilla-alanjstrBugs → cst
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Reporter | ||
Updated•19 years ago
|
Summary: Add a note to the front page explaining that "1.0+" is not 1.0.x → Stop 1.0.x users trying to install 1.0+-only addons
| Assignee | ||
Comment 3•19 years ago
|
||
I changed the display string to "Deer Park". The form let me enter "Deer Park Alpha", but the database chopped it at 9 characters, so that's the best we're getting. I don't want to use something like "1.5alpha" because people will probably start thinking that's a valid maxver. I'm not going to make code changes to UMO1.0 for this (it's a can of worms). If someone else wants to, feel free to reopen the bug and take ownership of it.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 4•19 years ago
|
||
(In reply to comment #3) > I'm not going to make code changes to UMO1.0 for this (it's a can of worms). If > someone else wants to, feel free to reopen the bug and take ownership of it. This still isn't fixed - see https://addons.mozilla.org/extensions/moreinfo.php?application=firefox&id=1042&page=comments ; so marking WONTFIX based on comment 3.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Version: unspecified → 1.0
| Reporter | ||
Updated•19 years ago
|
Status: REOPENED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WONTFIX
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•