117063 - select box don't stays open with one click if tabs are used

Status: RESOLVED EXPIRED

(SeaMonkey :: Tabbed Browser, defect)

Description

[Wolfgang Rosenauer [:wolfiR]]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011221
Netscape6/6.1
BuildID:    

if there are tabs used a select-tag window don't stay open after a
one-click. You have to hold the mouse button to choose an item.
If you don't use tabs the box stays open until you choose an item with
a mouse click.

Reproducible: Always
Steps to Reproduce:
1.search a page with a select box
2.open a second tab
3.click on the select button

Comment 1

[Asa Dotzler [:asa]]

worksforme with 122808 mozilla linux build. I loaded several bugs in several
different tabs and all select boxes opened and stayed open with a single click
and release. 

Comment 2

[John Morrison]

I can reproduce this on Linux (but not win32 or macos9) [20011228nn builds]. 

The key thing, which is implicit in Wolfgang's steps to reproduce above, is to 
start with a new browser window with no tabs, then visit, e.g., 
http://bugzilla.mozilla.org/query.cgi, then do Ctrl-T to get a new tab, and 
finally to return to query.cgi and try to drop down one of the select controls.
The drop-down will no longer stay open after you click on it; it will rollup
when it hears the 'mouseup' event.

It appears that when the second tab window is created, the view of query.cgi
is confused by the downward shift in the position of that page (or hand-waving 
to that effect.

If you subsequently reload query.cgi in the same tab, everything gets synched 
up again and the drop-down menu will stay open after you click on it.

-> bryner sounds like he wants this :-]

Comment 3

[Brian Ryner (not reading)]

-> 0.9.9, this is fixed by xbl selects.

Comment 4

[Brian Ryner (not reading)]

XBL form controls will not be turned on for 0.9.9.  -> 1.0.

Comment 5

[scottputterman]

Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+,
topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword.  Please send any
questions or feedback about this to [e-mail].  You can search for
"Moving bugs not scheduled for a project" to quickly delete this bugmail.

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420