236828 - Wrong keyboard order in target selection combo in the "Open Web Location" dialog.

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Christian Ullrich]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040306 Firebird/0.8.0+
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040306 Firebird/0.8.0+

There are three options in the combo box (current window, new window, new tab).
The cursor keys move through the options in the wrong sense (cursor down makes
the selection go up, and vice versa). This is similar to bug #227801, but it's a
different dialog.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Neil Paris]

This was filed in the wrong component. Firefox doesn't have a "Open Web
Location" dialog, but Mozilla does, and I can see the behavior in mozilla.

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3) Gecko/20040921

Clicking on the "Open In" box, I can arrow up/down and get to the first and the
third choice, but never the second or fourth choices; However, if I click inside
there and choose "New Navigator Window", then I can only up/down to the second
and fourth entries, and never the first or third.

Comment 2

[Serge Gautherie (:sgautherie)]

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910] (release) (W2Ksp4)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.13) Gecko/20060414] (release) (W2Ksp4)

1. (Ctrl+Shift+L) Open "File > Open Web Location".
2. ...

WorksForMe, on Windows 2000.

NB:
*I have "Current window / New window / New tab / separator / New composer".
*Mouse clicking on the label or the list itself, or "Tab-ing",  makes no difference.

*****

MozillaAS v1.7.x is not supported anymore.

Can you reproduce with SeaMonkey v1.1.9 (Linux) ?

Comment 3

[Tony Mechelynck [:tonymec]]

SeaMonkey 1.1.x is not supported anymore either.

I cannot reproduce on this build:
Mozilla/5.0 (X11; Linux x86_64; rv:2.0.2pre) Gecko/20110518 Firefox/4.0.2pre SeaMonkey/2.1.1pre

Also no reply to comment #2.

If this problem is seen in SeaMonkey 2.0.14 or later (preferably 2.1 or later), please open a new bug.