83422 - Cannot type/click in url area after minimizing download window

Status: VERIFIED FIXED

(SeaMonkey :: Location Bar, defect)

Description

[Christoph]

Build: 2001053004 (and earlier)
Platforms: Win98, WinME

1) Download any file (preferably a larger one so this will be seen)

2) Choose how and where to save the file

3) When download starts and download window is showing progress, minimize the
download window

4)Try to click in or type anything in the address box on the navigation toolbar

Result: Can't click or type anything in the box.

However, if you don't minimize download progress window and instead click
directly in the address box or click on the browser to bring it to the
foreground, you are free to enter a URL or cursor in the area.

Comment 1

[Christoph]

Forgot to add it happens in both Classic and Modern skins

Comment 2

[doctor__j]

Confirming bug on Win32 build 20010530043.

Workaround: Press Ctrl-L to switch focus to URL Bar.

Comment 3

[Asa Dotzler [:asa]]

over to Apps

Comment 4

[Doron Rosenberg (IBM)]

->xpapps

Comment 5

[Doron Rosenberg (IBM)]

->xpapps

Comment 6

[sairuh (rarely reading bugmail)]

->urlbar

Comment 7

[sairuh (rarely reading bugmail)]

workaround: if you *don't* minimize the download progress dialog, you can still
access the urlbar. interestingly, once i start typing there, the progress dialog
minimizes itself. :)

Comment 8

[sairuh (rarely reading bugmail)]

also: i tested my workaround on mac and linux as well as winnt, and it works
fine. [used 2001.06.07.1x comm branch bits.]

Comment 9

[Alec Flett]

reassign url bar bugs to new owner..

Comment 10

[saari (gone)]

Is the download window a dialog or a toplevel window? Do we see this on anything
other than WinME?

Comment 11

[Christoph]

Haven't seen this happen since I first reported it - must've gotten fixed or 
fixed itself months ago.  Gonna mark it fixed unless somebody else still sees 
this...I don't anymore.

Comment 12

[sairuh (rarely reading bugmail)]

mass-verifying claudius' Fixed bugs which haven't changed since 2001.12.31.

if you think this particular bug is not fixed, please make sure of the following
before reopening:

a. retest with a *recent* trunk build.
b. query bugzilla to see if there's an existing, open bug (new, reopened,
assigned) that covers your issue.
c. if this does need to be reopened, make sure there are specific steps to
reproduce (unless already provided and up-to-date).

thanks!

[set your search string in mail to "AmbassadorKoshNaranek" to filter out these
messages.]