Closed
Bug 285094
Opened 19 years ago
Closed 19 years ago
Fixes for xpi-file
Categories
(Core Graveyard :: XForms, defect)
Core Graveyard
XForms
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: allan, Assigned: allan)
References
()
Details
Attachments
(1 file)
1.20 KB,
patch
|
doronr
:
review+
|
Details | Diff | Splinter Review |
We've seen more than one trying to install the xforms.xpi package on non-nightly builds. If we just change the version number in install.rdf, that should solve it afaik.
Assignee | ||
Comment 1•19 years ago
|
||
Has "1.0+" has minimal version, "1.0" is wrong. It also inserts a homepage URL and a comment.
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•19 years ago
|
Attachment #176553 -
Flags: review?(aaronr)
Comment 2•19 years ago
|
||
Comment on attachment 176553 [details] [diff] [review] Patch for install.rdf r=me
Attachment #176553 -
Flags: review?(aaronr) → review+
Comment 3•19 years ago
|
||
r=me too
Assignee | ||
Comment 4•19 years ago
|
||
Checked in.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•19 years ago
|
||
With a build from this morning I get the following error when I try to install the xforms.xpi nightly: "Mozilla XForms 0.1 could not be installed because it is not compatible Browser 1.0+. (Mozilla XForms 0.1 will only work with Browser 1.0+)" Huh?!
Comment 6•19 years ago
|
||
This is because of bug 285658 (firefox trunk says its still 1.0 to extension manager).
Assignee | ||
Comment 7•19 years ago
|
||
(In reply to comment #6) > This is because of bug 285658 (firefox trunk says its still 1.0 to extension > manager). I've pulled this one out again, until bug 285658 is fixed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 8•19 years ago
|
||
Checked in again, since bug 295538 is now checked in.
Status: REOPENED → RESOLVED
Closed: 19 years ago → 19 years ago
Depends on: 295538
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•