Closed
Bug 422765
Opened 18 years ago
Closed 18 years ago
Javascript Debugger XPI won't install to Firefox 3.0b4
Categories
(Other Applications Graveyard :: Venkman JS Debugger, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: rginda)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4
Even though the add-on page for the Javascript Debugger states that the extension is compatible up through beta 4 of Firefox 3 (3.0b4pre) it won't install and stops with an error of "JavaScript Debugger 0.9.87.2 could not be installed because it is not compatible with Firefox 3.0b4".
In looking at the "install.rdf" file I found that the max version for Firefox 3.0 compatibility is set at "3.0b2".
<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<em:minVersion>0.9</em:minVersion>
<em:maxVersion>3.0b2</em:maxVersion>
</Description>
</em:targetApplication>
Saving the XPI locally and editing the install.rdf file to have the correct max version of "3.0b4" allows the extension to be installed.
Reproducible: Always
Steps to Reproduce:
1. Install/run Firefox 3 beta 4
2. Navigate to Javascript Debugger Mozilla Add on URL "https://addons.mozilla.org/en-US/firefox/addon/216"
3. Click on "Install Now" button.
Actual Results:
Javascript Debugger would not install and modal dialog with the following message is displayed, "JavaScript Debugger 0.9.87.2 could not be installed because it is not compatible with Firefox 3.0b4."
Expected Results:
Javascript Debugger installed and prompted to restart Firefox before using.
Updated•18 years ago
|
Assignee: nobody → rginda
Component: Extension Compatibility → JavaScript Debugger
Product: Firefox → Other Applications
QA Contact: extension.compatibility → venkman
Comment 1•18 years ago
|
||
There's been a new version in the Queue for some time now, but there's a big backlog in the queue so it's taking it's time. I've updated the current version (which isn't at the top of the list in the dev cp, which is why I'd missed it) now --> FIXED.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•