157715 - [10.2] Opened menu blocked if Save As sheet appears

Status: RESOLVED WONTFIX

(Camino Graveyard :: General, defect)

Description

[Stephane Moureau]

If you make a Ctrl-click to ask a Save As for an archive, there is always a
small delay (1-2 seconds) before the Save As sheet appears. In the mean time,
click on the menu bar to show a menu (e.g. File) and see its contents, wait with
the menu opened, the Save As sheet appears and everything is blocked. If you are
lucky, you can still reach the Save button if the menu does not cover it.
v0.40 Build 20020715 16:03

Comment 1

[Greg K.]

WorksForMe using Chimera/20020715. I choose "Save Page As..." from the
contextual menu (no "Save As..." item is shown), and before I can select
anything from the File menu, a Save *dialog* (not sheet) is shown.

Comment 2

[Stephane Moureau]

Attachment: covered

covered

Comment 3

[Brad Kemper]

In 2002111912, I _can_ repeat this bug.

Clicking on "File" before the "Save" window comes up causes that window to be
behind the menu layer. The window can be moved around, but the menu can not be
dismissed. Menus opened between the clicking of the link and the appearance of
the the "Save" window should be closed.

P.S. why is "save" a window instead of a sheet?

Comment 4

[Simon Fraser [no longer active]]

*** Bug 168458 has been marked as a duplicate of this bug. ***

Comment 5

[Mike Pinkerton (not reading bugmail)]

over to me

Comment 6

[Simon Fraser [no longer active]]

See also bug 187047 and related bugs. We have a bunch of situations that can get
you into a blocked state (need tracking bug).

Comment 7

[Samuel Sidler (old account; do not CC)]

I can *definitely* duplicate this.

Comment 8

[Simon Fraser [no longer active]]

On 10.4.4, I can click on the buttons in the save panel even while a menu is up, so am not in a locked state here. Hitting keys (e.g. Escape) also works.

Comment 9

[Simon Fraser [no longer active]]

*** Bug 187047 has been marked as a duplicate of this bug. ***

Comment 10

[Simon Fraser [no longer active]]

*** Bug 200397 has been marked as a duplicate of this bug. ***

Comment 11

[Samuel Sidler (old account; do not CC)]

If this is 10.2 only, should it be resolved WONTFIX since we're dropping support for 10.2? Or is there need to fix this specifically for our 1.0.x users?

Or... since the bug *does* exist on 10.4 (there's just a workaround), should we keep it open? Or does the workaround constitute a "fix"?

Comment 12

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

This should be covered by bug 181721 on 10.3/10.4.

The 10.2 ship has sailed.