Closed Bug 206504 Opened 21 years ago Closed 21 years ago

Views dropdown menu quickly loses focus/highlight

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.4final

People

(Reporter: nbaca, Assigned: sspitzer)

References

Details

(Keywords: crash, regression)

Attachments

(1 file)

Trunk build 2003-05-20: WinMe, Mac 10.1.5, Linux RH 8

Overview: Move the cursor over the Veiws dropdown menu items and notice that it
highlights an entry and quickly unhighlights. Because of this it is difficult to
choose the Customize option. 

Steps to reproduce:
1. Click on the Views dropdown
2. Move the cursor to any item in the drop down list 
3. Now try to move the cursor to the Customize option at the bottom

Actual Results: The Views dropdown menu closes before I havea chance to select
Customize to open the Customize Message Views dialog.

Expected Results: When the cursor lands on a views dropdown item, it should
remain higlighted until the cursor moves.
Marking nsbeta1 because this was working as of build 2003-05-06. It's also
confusing/frustrating for the Views dropdown to lose focus or to close when
trying to select the Customize item. It should be fixed for this release.
Keywords: nsbeta1, regression
QA Contact: esther → nbaca
Sarah, have you seen this problem in any of the browser windows?
hm, out of curiosity i tried reproducing this by using the down arrow key (after
clicking to expand View dropdown menu with mouse). i got into a state where
focus was gone (couldn't move the highlight), and the app crashed. occurred on
both my linux box and Ninoschka's OS X machine.

no talkback appeared, so am going to see if i can get a crash report.
nbaca mentioned that this wasn't a problem with 5/6 builds. will get regression
window in a moment.

i'm not sure if the crash i saw is related. if it isn't, feel free to remove the
crash kw, and i'll spin off another bug. here's the top of the trace:

Thread 0 Crashed:
 #0   0x001d6efc in nsCOMPtr_base::begin_assignment()
 #1   0x012c2b08 in nsXULElement::GetAttr(int, nsIAtom*, nsAString&) const
 #2   0x010b0710 in nsMenuFrame::IsDisabled()
 #3   0x01351ad0 in nsMenuFrame::MenuIsDisabled(int&)
 #4   0x010aaee4 in nsMenuPopupFrame::KeyboardNavigation(unsigned, int&)
 #5   0x010b0334 in nsMenuFrame::KeyboardNavigation(unsigned, int&)
Severity: normal → critical
Keywords: crash
works fine with 2003.05.07.03, broken in 2003.05.08.08.
i've checked a couple of dropmenus in the preferences dialog (eg, Fonts,
Navigator and Languages), and i couldn't repro the problems that nbaca and i
saw. nor can i repro with the dropmenus in the JMC dlg. perhaps it's specific
only to View in the mailnews 3pane...
I got the crash, too, (same recursive stack) when using the keyboard (not the
mouse).

I'll go look through the checkins.
Status: NEW → ASSIGNED
working on this for 1.4 final
Target Milestone: --- → mozilla1.4final
so, my apologies to sarah and bryner.

I was so sure this wasn't me, that I dragged bryner into it.

and 5 minutes later, he tells me it was me.

my only defense (which is paper thin) is that couldn't reproduce this on my
debug build at home, but I could at work.

but that's not excuse.

here's the fix:

Index: resources/content/msgViewPickerOverlay.js
===================================================================
RCS file: /cvsroot/mozilla/mailnews/extensions/mailviews/resources/content/msgVi
ewPickerOverlay.js,v
retrieving revision 1.7
diff -r1.7 msgViewPickerOverlay.js
221c221
<   viewPicker.selectedItem = document.getElementsByAttribute("value", aValue)[0
];
---
>   viewPicker.selectedItem = viewPicker.getElementsByAttribute("value", aValue)
[0];
fixed.  also thanks to nbaca and sarah for finding and tracking this one down.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Keywords: nsbeta1nsbeta1+
Resolution: --- → FIXED
Is this related to bug 206315 at all?
*** Bug 206315 has been marked as a duplicate of this bug. ***
Seth wrote:

> here's the fix:

viewPicker.selectedItem = viewPicker.getElementsByAttribute("value", aValue)[0];

Actually, you should have used all along:

viewPicker.value = aValue;
thanks neil.  I'll try that in my tree, and it will land in 1.5.
Trunk build 2003-05-22: WinMe, Mac 10.1.5, Linux RH 8
Verified Fixed. Using the mouse or the arrow keys work as expected (focus
remains on the View dropdown item based on cursor location) and without a crash.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: