Open Bug 456814 (msgreadertracker) Opened 11 years ago Updated 5 years ago
Message reader enhancements (tracker/meta bug) [incl
. new header pane changes]
+++ This bug was initially created as a clone of Bug #449691 +++ This bug will track each individual suggested change to the message reader through dependent bugs. The milestone & blocking flag are used to keep it on radar -- each sub issue will get its own flag & milestone treatment.
Adding depends and blockers from bug 449691.
I just filed bug 458661, which may also be related to this work.
I just filed two message reader related bugs (please include in dependent list of this bug) Bug 460602 RFE: Message reader: Remove visual clutter of dropdown arrows for each address Bug 460605 Message Reader: header pane context menu popup takes too long for contacts in long list with lots of addresses The following bug is also message reader related, and might be an idea for the first Mozilla Messaging version of Thunderbird to "raise the bar" and catch up with usability features that have long been in MS Outlook express, e.g. the ability of selecting and copying more than just one address from a given header with multiple addresses (It is also a regression from Netscape 4...) Bug 167010 can't select text to copy email addresses in message header Finally, I love the new yellow stars for bookmarking new addresses, as well as tabbed email, good stuff, carry on like that...
Target Milestone: Thunderbird 3.0b1 → Thunderbird 3.0b2
Bug 418424 absent email signature disclaimer is unsatisfactory :clarkbw is cited @ https://bugzilla.mozilla.org/show_bug.cgi?id=418424#c15 for integrating that bug into the new Message Reader layout. Recommend addition to this tracker.
Bug 226468 - Contacts sidebar in Thunderbird lacks "Add to BCC:" button.
Bumping off the b2 blocker list as these aren't going to get finished with the time available. We will have to do a big push on these message reader bugs in the next milestone.
Target Milestone: Thunderbird 3.0b2 → Thunderbird 3.0rc1
Summary: Message reader enhancements (tracker) → Message reader enhancements (tracker/meta)
Component: Mail Window Front End → Message Reader UI
QA Contact: front-end → message-reader
Meta bugs can't block. I've triaged all the dependent bugs in this tree and marked the appropriate ones as blocking.
Flags: blocking-thunderbird3+ → blocking-thunderbird3-
The following bug covers a (larger) subset of this bug and should be closed to avoid confusion: Bug 513553 [Meta bug] Tracking bug for changes in header pane in Thunderbird 3 Maybe the reason why that "new header" meta bug was opened was that this bug's current summary ("Message reader enhancements (tracker/meta)") doesn't have some of the important keywords that might be needed to find it. I know developers will hate me for this, but in the interest of improved retrievability I suggest adding "[incl. new header pane changes]" to the summary, so that e.g. the following searches will return this bug: - [New] Message Reader [changes | enhancements | meta bug | tracker bug] - [New] Header Pane [changes | enhancements | meta bug | tracker bug] I resisted adding the word "tracking" as well ;)
Summary: Message reader enhancements (tracker/meta) → Message reader enhancements (tracker/meta bug) [incl. new header pane changes]
Target Milestone: Thunderbird 3.0rc1 We are WAY past 3.0rc1, so should change the milestone. Thanks.
Can we get a NEW milestone?
(In reply to Worcester12345 from comment #11) > Can we get a NEW milestone? We generally do not target bugs to a specific release unless they have actually been fixed, in which case it is more a pointer to the release they will be include in. Sometimes developers actively working on bugs may set a specific milestone. We do this for multiple reasons, including not setting false expectations when we don't have people allocated to work on the issue. If you disagree with this policy or the setting for this bug, please discuss on tb-planning which is better suited to this sort of discussion than bugzilla.
(In reply to Mark Banner (:standard8) from comment #12) > (In reply to Worcester12345 from comment #11) > > Can we get a NEW milestone? > > We generally do not target bugs to a specific release unless they have > actually been fixed, in which case it is more a pointer to the release they > will be include in. Sometimes developers actively working on bugs may set a > specific milestone. We do this for multiple reasons, including not setting > false expectations when we don't have people allocated to work on the issue. > If you disagree with this policy or the setting for this bug, please discuss > on tb-planning which is better suited to this sort of discussion than > bugzilla. What is "tb-planning"? I will check it out if you help me find it. I thought the "Milestone" is something you were using as a checkpoint for where this should be fixed.
No, only when for which release it *was* fixed. tb-planning: https://mail.mozilla.org/listinfo/tb-planning
You need to log in before you can comment on or make changes to this bug.