Using apr26 m16 commercial builds Logging this as a tracking mechanism to get basic navigation among messages in a folder to work from within the standalone message window. Currently nothing works navigationally speaking. Doesn't work from menu items or toolbar buttons or shortcut. Go next message Go next unread message Go next unread thread etc.

there's a good possibility this won't work for this release.

What?! People who use the standalone window would have to open each and every message to a window? That'll go over like a lead balloon.

First of all, to the PDT+ team who will evaluate this, please don't hold up beta 2 for this bug, that's why I marked it M18. Second of all, when discussing the standalone message window on n.p.m.mail-news, people didn't seem so concerned about this. In fact, it seems that the people who use the standalone window regularily actually do open a window for each message. I've seen it in action myself and it's pretty insane.

I just read the standalone message window thread in the mail-news newsgroup, and I'm amazed! Whatever. It seems to me like it's not a good thing to cut this, but I guess when this hits a Mail Issues meeting we'll arrive at some consensus.

BTW, I'm not suggesting we remove the nsbeta2, I'm just giving my input for when they review it. I should add, that this might be hard to implement. I have some ideas and it might show up as early as M16 if I get views with unread messages to work the way I think they will work.

PDT would like to know whether this is really a bug or a feature. If it's a bug, it can be M18, but it can't be M18 if it's a feature. Also would like Kevin Murray's opinion on whether navigation in the standalone msg window is a requirement.

it's a feature and we pretty much decided that this isn't a necessity for the product in today's issues meeting.

Putting on [nsbeta2-] radar. Not critical to beta2.

moving to future milestone.

I agree with laurel. While many standalone-msg-win users don't use "Next", enough of them do. It would be a "missing" feature. But if I see the other bugs that are cutted, it is only consistent to cut this as well :-/.

*** Bug 54510 has been marked as a duplicate of this bug. ***

It seems like anyone who uses standalone message as their preferred way to read messages (like me) is going to need to do "next" "delete" etc. from that view

Laura, delete works. Next is not needed for *everyone*. In fact, I read mail for years without using it. In agree, that *many* users will want to have it, at least as option.

I agree that we would like to have this in, but unfortunately it didn't make it in. We did ask around, including on the n.p.m.mail-news newsgroup and the response was that most people used the standalone message window in the following way: 1. Select a message in the thread pane. 2. Open up a standalone and read the message. 3. close the standalone 4. Scroll to another message in the thread pane and repeat the process. Although not a scientific study that was a lot of the response we got which made it seem like an ok tradeoff to not do this feature and work on other things.

Additionally, I went through the keyboard accelerator spec and prioritized items according to what I thought were *basic* key nav functions, which we were in danger of not having. Let me know if you'd like to follow up offline, as this specific bug isn't necessarily the place for that conversation.

*** Bug 58486 has been marked as a duplicate of this bug. ***

reassigning to sspitzer

adding nsbeta1- keyword. Will hopefully work on architecture that will make this easier to implement in the future.

*** Bug 64196 has been marked as a duplicate of this bug. ***

*** Bug 64197 has been marked as a duplicate of this bug. ***

accepting.

moving to mozilla 0.9, as we'll be doing some of this work in 0.8 putterman, please correct me if I'm wrong.

I'd like to keep this in the future milestone because we don't know how easy this will be and we decided we didn't want to go out of our way to implement it. If it turns out that this is really easy to do based on the other work we are doing for 0.8 then we can revisit it.

*** Bug 64921 has been marked as a duplicate of this bug. ***

marking nsbeta1+. This will get fixed when the perfbranch lands. reassigning to mscott since he worked on this.

I'm pretty sure this got fixed when we landed on 3/16.

fixed.

OK with apr4 commercial trunk builds, all platforms. Basic navigation working from message window. Any specific issues with navigation from the message window will be logged separately.