Closed
Bug 330168
Opened 18 years ago
Closed 18 years ago
Phishing State should take precedence over Junk State in the message bar
Categories
(SeaMonkey :: MailNews: Message Display, defect)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey1.1alpha
People
(Reporter: iannbugzilla, Assigned: iannbugzilla)
Details
(4 keywords)
Attachments
(1 file)
5.72 KB,
patch
|
neil
:
review+
Bienvenu
:
superreview+
dveditz
:
approval1.8.0.2+
kairo
:
approval-seamonkey1.0.1+
kairo
:
approval-seamonkey1.1a+
|
Details | Diff | Splinter Review |
This is the mailnews version of TB bug 298525. Precedence order should be Phish, Junk and then remote content.
This patch: * Swaps order of deck, and related JS, so that phishing takes precedence over junk bar * Updates comment to reflect new order * Removes unused variable isCurrentlyNotJunk
Updated•18 years ago
|
Attachment #214779 -
Flags: review?(neil) → review+
Attachment #214779 -
Flags: superreview?(bienvenu)
Updated•18 years ago
|
Attachment #214779 -
Flags: superreview?(bienvenu) → superreview+
Comment on attachment 214779 [details] [diff] [review] Simple patch v0.1 (Checked in trunk & branch 1.8 / 1.8.0) Checking in (trunk) mailWindowOverlay.js; new revision: 1.230; previous revision: 1.229 mailWindowOverlay.xul; new revision: 1.307; previous revision: 1.306 done
Attachment #214779 -
Attachment description: Simple patch v0.1 → Simple patch v0.1 (Checked in trunk)
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment on attachment 214779 [details] [diff] [review] Simple patch v0.1 (Checked in trunk & branch 1.8 / 1.8.0) Rqeuesting a= for SM1.0.1 and SM1.1a
Attachment #214779 -
Flags: approval-seamonkey1.1a?
Attachment #214779 -
Flags: approval-seamonkey1.0.1?
Comment 4•18 years ago
|
||
Comment on attachment 214779 [details] [diff] [review] Simple patch v0.1 (Checked in trunk & branch 1.8 / 1.8.0) low-risk security-relevant fix, should be consistent in all new releases, a=me for both 1.1 and 1.0.1
Attachment #214779 -
Flags: approval-seamonkey1.1a?
Attachment #214779 -
Flags: approval-seamonkey1.1a+
Attachment #214779 -
Flags: approval-seamonkey1.0.1?
Attachment #214779 -
Flags: approval-seamonkey1.0.1+
Comment on attachment 214779 [details] [diff] [review] Simple patch v0.1 (Checked in trunk & branch 1.8 / 1.8.0) Checking in (branch 1.8) mailWindowOverlay.js; new revision: 1.222.2.7; previous revision: 1.222.2.6 mailWindowOverlay.xul; new revision: 1.298.2.8; previous revision: 1.298.2.7 done
Attachment #214779 -
Attachment description: Simple patch v0.1 (Checked in trunk) → Simple patch v0.1 (Checked in trunk & branch 1.8)
Keywords: fixed-seamonkey1.1a
Comment on attachment 214779 [details] [diff] [review] Simple patch v0.1 (Checked in trunk & branch 1.8 / 1.8.0) Requesting a= for 1.8.0.2 as suggested by dveditz
Attachment #214779 -
Flags: approval1.8.0.2?
Comment 7•18 years ago
|
||
Comment on attachment 214779 [details] [diff] [review] Simple patch v0.1 (Checked in trunk & branch 1.8 / 1.8.0) approved for 1.8.0 branch, a=dveditz for drivers
Attachment #214779 -
Flags: approval1.8.0.2? → approval1.8.0.2+
Comment on attachment 214779 [details] [diff] [review] Simple patch v0.1 (Checked in trunk & branch 1.8 / 1.8.0) Checking in (branch 1.8.0) mailWindowOverlay.js; new revision: 1.222.2.3.4.4; previous revision: 1.222.2.3.4.3 mailWindowOverlay.xul; new revision: 1.298.2.2.4.7; previous revision: 1.298.2.2.4.6 done
Attachment #214779 -
Attachment description: Simple patch v0.1 (Checked in trunk & branch 1.8) → Simple patch v0.1 (Checked in trunk & branch 1.8 / 1.8.0)
Keywords: fixed-seamonkey1.0.1
Comment 9•18 years ago
|
||
This was seamonkey only, but we had to approve the patch to land on the 1.8.0 branch. It landed on 3/17/06, but not marked fixed1.8.0.2 as it is seamonkey only. It still shows up on the NeedsLanding list because it is approved for 1.8.0.2 but not marked fixed1.8.0.2. Should we mark it fixed1.8.0.2 or take off the approval flag?
Updated•18 years ago
|
Keywords: fixed1.8.0.2
Updated•18 years ago
|
Keywords: fixed1.8.1
You need to log in
before you can comment on or make changes to this bug.
Description
•