Closed Bug 224728 Opened 21 years ago Closed 19 years ago

Bad UI behaviour with Message Compose Window pressing ALT and UP/DOWN key

Categories

(Thunderbird :: Message Compose Window, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: knocte, Assigned: mscott)

References

Details

(Keywords: access)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.5) Gecko/20031007 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.5) Gecko/20031007 When composing a new message, if we use the cursor key "down", a component drops down incorrectly. Reproducible: Always Steps to Reproduce: 1. Press CTRL+M to open a new message window. 2. Press the FROM bar to select an identity. 3. Press it again so as an identity has been selected and the focus is on that element. 4. Press ALT key. 5. Press down cursor key. Actual Results: The first menu drops down but the FROM bar (to select identities) also drops down. If in that situation, we click on another Mozilla window (that is, for example, behind the message compose window) another bug occurs: the menu "File" that has dropped down still is showing on the window. Expected Results: Drop down the first menu ("File") and nothing more. If we click on other Mozilla page, the dropped down menu should disappear also.
Note that step (4) should be "Press and release ALT key". Also, once the two menus are displayed, typing ESC closes the File menu; at this point, the From: dropdown has the focus again. Switching to another window in these cases results in oddness, as well: If you switch to another window with both menus displayed, the From: dropdown closes but the File menu floats on top of the newly-active window. If you switch to another window after typing ESC to close the File menu, the From: dropdown menu floats on top of the newly-active window. Couldn't find a dupe, altho it's hard to know what to search for with a bug like this. Confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Yes, I had also tried to find a dupe but it's difficult to know what to search. I am changing the summary because I have noticed that the bug happens also with the "up cursor key". Thanks for reviewing it, Mike.
Summary: Bad behaviour with Message Compose Window pressing ALT and DOWN key → Bad behaviour with Message Compose Window pressing ALT and UP/DOWN key
confirming with build 20031028 WinXP
This is an accessibility problem for people with disabilities, raising severity.
Severity: minor → normal
Keywords: access
It seems on Linux this bug is also present, but the way to reproduce it is different (because in Linux if you press and release the ALT key, the menu doesn't get the focus). The steps to reproduce on Linux are: 1. Press CTRL+M to open a new message window. 2. Press the FROM bar to select an identity. 3. Press it again so as an identity has been selected and the focus is on that element. 4. Press ALT+F (for example, to open the "File" menu). 5. Press up/down cursor key. Changing OS to a 'All'.
OS: Windows XP → All
I can reproduce this bug easily under Mozilla 1.7.2, Win2K, with Classic and Pinball (Modern-based) themes -- but under Mozilla 1.8a5, it appears to be fixed. Reporter (knocte), can you confirm? However, TB 0.8 and 0.8+1029 both still exhibit the symptom.
Confirming that with build 2004103106[Win32] it is fixed. So, is there a way to close this bug for Moz-suite and leave it open for TB?
Summary: Bad behaviour with Message Compose Window pressing ALT and UP/DOWN key → Bad IU behaviour with Message Compose Window pressing ALT and UP/DOWN key
Moving bug to Thunderbird.
Component: Mail Window Front End → Message Compose Window
Product: MailNews → Thunderbird
Version: Trunk → unspecified
Assignee: sspitzer → mscott
QA Contact: esther
Summary: Bad IU behaviour with Message Compose Window pressing ALT and UP/DOWN key → Bad UI behaviour with Message Compose Window pressing ALT and UP/DOWN key
This is working correctly in TB 1.5.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Confirming, this seems to be fixed in TB1.5. Marking verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.