Closed
Bug 565817
Opened 15 years ago
Closed 15 years ago
Seamonkey compatibility info should be pulled up to 2.1a2
Categories
(Cloud Services :: General, defect)
Cloud Services
General
Tracking
(Not tracked)
RESOLVED
FIXED
1.3
People
(Reporter: iav, Assigned: kairo)
Details
Attachments
(1 file)
|
829 bytes,
patch
|
mconnor
:
review+
|
Details | Diff | Splinter Review |
Seamonkey compatibility info should be pulled up to 2.1a2pre.
I did a new weave account creation and work with already existing account for weave hg:c05e15dc53b1 in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a5pre) Gecko/20100513 SeaMonkey/2.1a2pre
History and password engines was enabled.
All works as it should.
|
Assignee | |
Comment 1•15 years ago
|
||
Actually, even 2.1a2 should be fine, that's what AMO accepts now.
|
|
Assignee | |
Updated•15 years ago
|
Attachment #447125 -
Flags: review? → review?(mconnor)
|
||
Updated•15 years ago
|
Attachment #447125 -
Flags: review?(mconnor) → review+
|
|
Assignee | |
Comment 2•15 years ago
|
||
Thanks, pushed as http://hg.mozilla.org/labs/weave/rev/19c24f8a50bb
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Summary: Seamonkey compatibility info should be pulled up to 2.1a2pre → Seamonkey compatibility info should be pulled up to 2.1a2
Target Milestone: --- → 1.3
You need to log in
before you can comment on or make changes to this bug.
Description
•