Closed
Bug 271233
Opened 20 years ago
Closed 20 years ago
Update extension: EditCSS
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect)
addons.mozilla.org Graveyard
Public Pages
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: guimier+bugzilla, Assigned: Bugzilla-alanjstrBugs)
References
()
Details
(Whiteboard: In queue)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.5) Gecko/20041115 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.5) Gecko/20041115 Firefox/1.0
{A0A87DB2-80BA-493a-B22F-FAFBAEA3E0A2} EditCSS 0.2.3 is out for Firefox 1.0 and
is available at http://downloads.mozdev.org/editcss/editcss0.2.3.xpi
This should be in Developer tools category.
Reproducible: Always
Steps to Reproduce:
1. Open
https://update.mozilla.org/extensions/moreinfo.php?application=firefox&id=179&vid=696
2. Looking to the version (0.2.2 that is former) and to the MaxVer compatibility
(0.10 that is incorrect)
Actual Results:
Cannot be installed on Firefox 1.0, although it is said to be compatible (wrong
MaxVer number)
Expected Results:
-Version number should be 0.2.3
-MaxVer number should be 1.0
-Category should be "Developer tools"
Long time ago I filled the comment
https://bugzilla.mozilla.org/show_bug.cgi?id=264602#c8
but, I'm sorry : I don't know what I did bad :o)
Updated•20 years ago
|
Assignee: psychoticwolf → Bugzilla-alanjstrBugs
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 1•20 years ago
|
||
Bulk Moving Extension/Theme listing bugs to new component. (Filter: masslistingspam)
Component: Update → Listings
Product: mozilla.org → Update
Version: other → unspecified
Summary: Update EditCSS extension version to 0.2.3 and compatibilit MaxVer to Firefox 1.0 → Update extension: EditCSS
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Comment 2•18 years ago
|
||
AMO BUGSPAM FOR COMPONENT MOVE AND DELETE (FILTER ME)
Component: Listings → Web Site
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
•