Should be +/- straightforward, but I remember bug 425480 discussion...
Will not block on a bug without describing what problems it causes that warrant pushing back any release, i.e. why we cannot have alpha/beta testers or regular users encounter this bug. I just searched dependent bugs for 5 minutes and didn't find any evidence that this would be hazardous. From all I see, it's not completely spec-conformant now, probably not pretty, but doesn't do any harm.
blocking-seamonkey2.1: ? → -
See bug 452979 which had been marked as a security bug. I'm not sure this is worth blocking release.
Fixed in Bug 425480
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 425480
Also fixes bug 922530 and bug 909264 (including the parts that bug 970121 accidentally fixes for completeness.)
Assignee: nobody → neil
Attachment #8374028 - Flags: review?(philip.chee)
Bah, Bugzilla won't let me change the status directly from DUP to ASSI.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment on attachment 8374028 [details] [diff] [review] Proposed patch r=me [code inspection plus a few test cases in the referenced bugs]
Attachment #8374028 - Flags: review?(philip.chee) → review+
Status: ASSIGNED → RESOLVED
Closed: 10 years ago → 8 years ago
Resolution: --- → FIXED
Landed to comm-release for seamonkey 2.26.1 $ hg tip changeset: 20171:f226cb234deb branch: SEA_2_26_1_RELBRANCH tag: tip user: Neil Rashbrook <email@example.com> date: Fri Feb 21 01:04:01 2014 +0000 summary: Bug 562845 Port bug 546013 bug 922530 bug 909264 r=Ratty
You need to log in before you can comment on or make changes to this bug.