Closed Bug 266380 Opened 20 years ago Closed 20 years ago

Update Extension : Print

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect)

Product:
addons.mozilla.org Graveyard
Component:
Public Pages
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jeeradej, Assigned: Bugzilla-alanjstrBugs)

Details

(Whiteboard: tested-) 

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1

I would like to update my Print extension, which is now compatible with Firefox
1.0PR. The info is as below:

* Extension name:            Print
* Version number:            0.2.2
* Release date:              2004-10-20
* Author name:               Jeeradej Thaworntaweewong
* E-mail address:            mozdev@jeeradej.mailshell.com
* URL to extension homepage: http://a.domaindlx.com/joetzzz/mozdev/
* URL to .xpi file:          http://a.domaindlx.com/joetzzz/mozdev/print/print.xpi
* Size of .xpi file:         4 KB
* Description:               Add 'Print' to context menu
* Compatibility:             Firefox 0.8-1.0+

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Assignee: psychoticwolf → jedsbugs
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: need-testing
Assignee: jedsbugs → Bugzilla-alanjstrBugs
Same as bug 266382

> * Compatibility:             Firefox 0.8-1.0+

That's not what your install.rdf says.
Marking tested- until install.rdf is fixed.
Whiteboard: need-testing → tested-
According to the status whiteboard, your extension didn't work.  Please reopen
when the issues have been addressed.  Thanks.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
Component: Update → Listings
Product: mozilla.org → Update
Version: other → unspecified
AMO BUGSPAM FOR COMPONENT MOVE AND DELETE (FILTER ME)
Component: Listings → Web Site
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.