Open Bug 960713 Opened 10 years ago Updated 8 years ago

Message Pane keeps opening

Categories

(SeaMonkey :: MailNews: Message Display, defect)

SeaMonkey 2.23 Branch
x86_64
Windows Vista
defect
Not set
normal

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: myhrddin, Unassigned)

References

Details

(Keywords: regression, regressionwindow-wanted)

User Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23 (Beta/Release)
Build ID: 20131210201652

Steps to reproduce:

I've repeatedly gone to layout and turned it off.  We need to be able to Lock down the layout once its in its preferred state.  Some of my clients are getting older and whatever they're doing with the mouse, its popping that pane open again.

And, today I had it happen to me.  I'm not sure if I did something that caused it to open and probably couldn't repeat it.

But, if the layouts could be locked once set, I believe that would cure any issues of the sort.
I wonder if this is caused by the notificationbox trying to show a notification?
It does not seem to be happening at the same time as notifications.  When it happened to me (and I've been using this line of software since well, the first release of mosaic I guess) I think I was either clicking the junk or delete button in the toolbar at the top.

I've just got a feeling that if we could lock down those layouts once they're the way we want them, it could make this a non-issue. I've always had my clients, regardless of email client, never have a preview pane open in email since, to me, its really opening the message and there are So Many they should deal with without ever opening them at all.

I realize it could be a large shift in layout management to be able to lock various layouts down once they're customized but, with an expanding base of older folks using the net and the slip-slides I know they're doing when they try to right or double click on things, this could be a very beneficial change.

We already lock down task bars, and things like docks once they're configured so it is already a relatively common method of keeping a setup in place, once configured.
See Also: → 1108389
You need to log in before you can comment on or make changes to this bug.