Cascading Menu for File Message or Move Message is too jumpy if you don't to through root of each level

RESOLVED EXPIRED

Status

--
minor
RESOLVED EXPIRED
16 years ago
13 years ago

People

(Reporter: jay, Unassigned)

Tracking

Trunk
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202

The new (compared to NS 4.76) cascading file/move message menu is great -- and
it works too! Wow!

But, while you navigate DEEP menus systems, the menu gets too jumpy and opens
the wrong folder level UNLESS you 

a) _click_ to open each level (instead of simply sliding to the flyout that
opens whether or not you click) AND 

b) slide OVER the "root" (the grayed out "File here") of the newly opened menu
level.

I am using IMAP and have very deep folder structures, but I don't think that
this is an IMAP issue.  The IMAP does not support messages and folders in a
folder.  Thus folders only contain folders OR messages.

(This Mozilla is running on Linux Red Hat 8 but is being viewed on a Windows 95
PC running the Linux/Gnome desktop through Cygwin XFree86 (4.2 I think) Xserver.)

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Actual Results:  
If you don't first click to open a folder level and then move "over and down"
passing over the grayed out "File here", the wrong folders are opened.

Expected Results:  
Moving diagonally (as long as you stay over the cascading menu) to a specific
folder should allow you to open that folder.  You should not _have_ to click to
open folder levels.  You should not _have_ to pass over the "File here" region
to prevent the menu from getting "jumpy".
Product: Browser → Seamonkey

Updated

14 years ago
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.