Closed Bug 268956 Opened 20 years ago Closed 20 years ago

Extensions not installing with Firefox 1.0

Categories

(Toolkit :: Add-ons Manager, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mhp3xr902, Assigned: bugs)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

A lot of the extentions listed at http://update.mozilla.org (in the extentions
section) don't seem to want to install in Firefox 1.0 (final).  I click on the
"install now" link in the extention page, and then a window pops up saying that
the extention isn't compatable, and it's compatable for versions 0.80 through
0.10 (instead of 1.00).

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
You know that 0.10 == 1.0 PR != 1.0 (Final version). So compatible to 0.10 does
NOT mean that this ext. is compatible to 1.0. Could you provide an example
extension or URL?
Summary: Extentions not installing with Firefox 1.0 → Extensions not installing with Firefox 1.0
this bug either reports the same problem as bug 260152 or is an u.m.o bug

Please, provide example urls.
I did not realize that.  However, the mouse gestures 1.0 plugin at

https://update.mozilla.org/extensions/showlist.php?application=firefox&version=1.0&numpg=&category=Mouse%20Gestures

States that it is compatable with 8.0 - 1.0.  But when I tried to install it at
the time I got the popup error message I listed here.  I tried installing that
and the others again today and all installed fine.  So I'm going to consider the
matter to be fixed.  Thanks for the info.

     --Dave
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
actually, it's worksforme then. Sorry for the spam
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → WORKSFORME
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.