Give informational messages in the thread pane when the thread pane is empty

NEW
Unassigned

Status

--
enhancement
19 years ago
2 years ago

People

(Reporter: jglick, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [adt2], URL)

(Reporter)

Description

19 years ago
Build: 2000-06-20-09-M17

If the user selects a folder or menu item which causes the thread pane to go 
blank, we should display text to the user to indicate what happened.

If the user selects: 
1. Folder with no messages in it.  Display in thread pane: "This folder does not 
contain any messages.  Please select another folder."
2. Folder unable to contain other messages (only other folders) (IMAP only. 
Display: "This folder can only contain other folders and contains no messages. 
Please select another folder."
3. If the user selects a view ("View" menu, "Messages") in which there are no 
available messages.  Display: "There are no messages available for the selected 
view. From the View menu, choose Messages to select another view."
(Reporter)

Comment 1

19 years ago
Nominate as nsbeta3
Keywords: nsbeta3
Target Milestone: --- → M18
(Reporter)

Comment 2

19 years ago
P4 per mail UE review.

Bug 45032 has been marked as a duplicate of this bug. Opps.
Priority: P3 → P4
(Reporter)

Comment 3

19 years ago
*** Bug 45032 has been marked as a duplicate of this bug. ***

Updated

19 years ago
QA Contact: lchiang → laurel

Updated

19 years ago
Whiteboard: [nsbeta3-]
Target Milestone: M18 → Future

Comment 4

19 years ago
Mail Triage is marking [nsbeta3-]

Comment 5

19 years ago
Adding myself to cc: list.

Comment 6

18 years ago
For (1), try `There are no messages in this folder.' It puts the important bit
(no messages) at the start of the sentence (making scanning easier), and it
doesn't patronize the user by assuming that if they open an empty folder they
must have intended to do something else instead.

Similarly for (2), `There are no messages in this folder. This folder can only
contain other folders.'
OS: Windows 98 → All
Hardware: PC → All
Summary: Messages in the thread pane when the thead pane is empty → Messages in the thread pane when the thread pane is empty
(Reporter)

Comment 7

18 years ago
Matthew's suggestions are good. Robin, unless you have any objections, lets go 
with:

If the user selects: 
1. Folder with no messages in it.  Display in thread pane: "There are no 
messages in this folder."
2. Folder unable to contain other messages (only other folders) (IMAP only). 
Display: "There are no messages in this folder. This folder can only
contain other folders." 
3. If the user selects a view ("View" menu, "Messages") in which there are no 
available messages.  Display: "There are no messages in this view. From the View 
menu, choose Messages to select another view."
(Reporter)

Comment 8

18 years ago
Add mail3 keyword. This would be nice to fix for 6.5.  As we saw in usability 
testing, users tend to get confused when the Thread Pane goes blank and it is 
not apparent to them why.
Keywords: mail3

Comment 9

18 years ago
reassigning to sspitzer
Assignee: putterman → sspitzer

Comment 10

18 years ago
*** Bug 41500 has been marked as a duplicate of this bug. ***

Comment 11

18 years ago
moving to mozilla0.8 and marking nsbeta1+.
Keywords: nsbeta3 → nsbeta1
Priority: P4 → P2
Whiteboard: [nsbeta3-] → [nsbeta1+]
Target Milestone: Future → mozilla0.8

Updated

18 years ago
QA Contact: laurel → nbaca

Comment 12

18 years ago
reassigning to chuang.
Assignee: sspitzer → chuang

Comment 13

18 years ago
moving to mozilla0.9
Target Milestone: mozilla0.8 → mozilla0.9

Comment 14

18 years ago
marking nsbeta1-
Keywords: nsbeta1 → nsbeta1-
Whiteboard: [nsbeta1+] → [nsbeta1+ 2/5]

Comment 15

18 years ago
I meant to move this to future.
Target Milestone: mozilla0.9 → Future

Updated

18 years ago
Keywords: nsCatFood

Comment 16

18 years ago
*** Bug 41501 has been marked as a duplicate of this bug. ***
(Reporter)

Updated

17 years ago
Keywords: mail3 → nsbeta1

Comment 17

17 years ago
reassigning to ssu
Assignee: chuang → ssu
Whiteboard: [nsbeta1+ 2/5]

Updated

17 years ago
QA Contact: nbaca → olgam

Updated

17 years ago
Keywords: nsbeta1 → nsbeta1+

Updated

17 years ago
Priority: P2 → P3

Updated

17 years ago
Target Milestone: Future → mozilla0.9.9

Updated

17 years ago
Blocks: 122274
Status: NEW → ASSIGNED
Keywords: nsbeta1+ → nsbeta1-
Target Milestone: mozilla0.9.9 → mozilla1.2

Comment 18

17 years ago
I remove nsbeta1- keyword - it was for MachV.
Keywords: nsbeta1-

Comment 19

17 years ago
Now I add 'nsbeta1' keyword for Buffy. Sorry, it's faster to edit multiple bugs
at once than manually go to each and remove minus.
Keywords: nsbeta1

Comment 20

16 years ago
per comment #8, users get confused, we should fix this as part of UI Polish, Jen
do you agree
QA Contact: olgam → esther
(Reporter)

Comment 21

16 years ago
Yes, i'd still like to see this implemented, especially with the new "Views" 
and Custom Views feature.

Comment 22

16 years ago
All of Jen's suggestions for display text in comment #7 are still valid with the
new custom Views feature. I'd also suggest that if the user chooses a custom
view from the View drop-down for which no messages are available, we should
display the text previously suggested by Jen: "There are no messages in this
view. From the View menu, choose Messages to select another view."



Comment 23

16 years ago
Mail triage team: nsbeta1+/adt2
Keywords: nsbeta1 → nsbeta1+
Whiteboard: [adt2]

Comment 24

16 years ago
CC'ing varga as this would probably need some help from tree code.

Comment 25

16 years ago
Do you want to keep tree column headers (subject, sender, etc) when displaying
such messages ?
Should it be dynamic ? I mean when you have no messages in your selected folder,
you get a message, but then something new appers in your folder, ...
I guess it should switch back to normal view then

Comment 26

16 years ago
You could define a new tree binding which would inherit from the one in tree.xml
and override treerows to be just a text
So when you need such behaviour you just set an attribute on the thread pane
tree which will switch to your custom binding.
And have another attribute for the message of course.

I don't know if there is a mechanism to be notified when something new appers in
selected folder, I guess there should be.

So we don't have to touch tree code directly.

I hope that there no oddities with XBL which would complicate this design :)
(Reporter)

Comment 27

16 years ago
>Do you want to keep tree column headers (subject, sender, etc) when displaying
>such messages ?

Yes.

>Should it be dynamic ? I mean when you have no messages in your selected
>folder, you get a message, but then something new appers in your folder, ...
>I guess it should switch back to normal view then

No msgs in Folder/View, show descriptive text. User does "Get Msgs" or mail
client set to get new msgs at set intervals, and there would now be a msg in
that folder/view, remove the descriptive text and replace with msg(s).

Comment 28

16 years ago
Sounds reasonable, thanks
So we can do what I described in comment 26.

Comment 29

16 years ago
> I don't know if there is a mechanism to be notified when something new appears
> in selected folder, I guess there should be.

The code that calls UpdateStatusMessageCounts() perhaps?

/me wonders how this will affect his theme's focusring XBL binding

I suppose I just need my own "focusring-with-text" binding?

Comment 30

16 years ago
>/me wonders how this will affect his theme's focusring XBL binding
>
>I suppose I just need my own "focusring-with-text" binding?

I don't know what your focusring XBL binding is, but as I said before you just
need a new XBL binding for <tree> which will override <treerows>

Updated

16 years ago
Target Milestone: mozilla1.2alpha → mozilla1.4beta

Comment 31

16 years ago
Robin, since this will introduce a UI and localization change, will it be
alright if I at least check in the string description to a .dtd file for the
5/15 deadline?

Comment 32

16 years ago
cc:'ing bobj, since there's L10N impact. Sean - this UI change does not affect
the help (but thanks for asking!).
Product: Browser → Seamonkey

Updated

11 years ago
Assignee: ssu0262 → mail
Severity: normal → enhancement
Status: ASSIGNED → NEW
QA Contact: esther
Summary: Messages in the thread pane when the thread pane is empty → Give informational messages in the thread pane when the thread pane is empty
Assignee: mail → nobody
Priority: P3 → --
QA Contact: message-display
Target Milestone: mozilla1.4beta → ---

Comment 33

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 34

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 35

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 36

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 37

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 38

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 39

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 40

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → EXPIRED

Comment 41

8 years ago
Still a useful enhancement.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: EXPIRED → ---

Updated

8 years ago
Status: REOPENED → NEW
You need to log in before you can comment on or make changes to this bug.