User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:126.96.36.199) Gecko/20100914 Ant.com Toolbar 2.0.1 Firefox/3.6.10 ( .NET CLR 3.5.30729; .NET4.0E) Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b6) Gecko/20100101 Firefox/4.0b6 For some reason, extensions whose homepage is hosted by Google Code have a problem. If you click the link for the actual extension, Google makes you download the XPI rather than installing it. Those who happen to be on Windows and use MR Tech's Toolkit are lucky. They can paste the XPI's URL into the File Open dialog and let Windows figure it out. For everyone else, all you can do is manually download the XPI and then install it. If users could right-click Google's link and select Install, it might be easier. Reproducible: Always Steps to Reproduce: 1. Visit any Google Code site for an extension. (http://searchboxsync.googlecode.com/ will do) 2.Attempt to install the extension direct from Google's link 3. Actual Results: Google makes you download the XPI and then install it. Expected Results: The process should be smoother. One step installs are the norm. Unfortunately, themes are typically just JAR files as far as the URL is concerned. Until the actual file comes down, you can't test it. So if someone wants to do a similar fix for themes hosted by Google Code, good luck.
The files are being served with the wrong MIME type: they need to be application/x-xpinstall. There's no way for Firefox to effectively solve this.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
(In reply to comment #1) > The files are being served with the wrong MIME type: they need to be > application/x-xpinstall. > > There's no way for Firefox to effectively solve this. Does that mean the add-ons manager handles a d&d of such a wrong mimetype differently? When I drag the link into the add-ons manager I get the software installation dialog.
Yes, it handles a DnD operation differently than Firefox does within a content page. For example, a DnD operation can come from places such as the local file system which will not be serving up a mimetype.
That makes absolutely sense. Thanks.
Status: RESOLVED → VERIFIED
Hardware: x86 → All
Version: unspecified → Trunk
You need to log in before you can comment on or make changes to this bug.