168644 - [10.4] Command+. keyboard shortcut doesn't cancel Open File... dialog

Status: RESOLVED INCOMPLETE

(Camino Graveyard :: Accessibility, defect, P4)

Description

[Michael Stillwell]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20020909
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20020909

The Command-. shortcut (for cancel) which works in practically every dialog in
OS X, doesn't work in Chimera.  For example, the Open File dialog (Command-O)
cannot be cancelled with Command-.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Greg K.]

Confirmed using Chimera/2002090913 on 10.1.5. Note that {escape} does work in
place of {command+.}.

Comment 2

[Dustin Voss]

This is because Command-. is used by the menu. According to Apple's docs,
Command-key shortcuts don't percolate up the responder chain like most events,
but drip down the view hierarchy.

I'd say this is by design, but one workaround would be to disable the "Stop
Loading" shortcut when a panel is frontmost.

Comment 3

[Brad Kemper]

What menu? Something should be done. I am very used to using command-period to
dismiss dialogs (sheets). It works in virtually every other application. In
Chimera, it is very unexpected that it does not work in "Add page to bookmarks"
or "Open Location". I always have to stop and think about using escape instead
(after I hear the system beep a couple times from my failed attempts).

Comment 4

[Brad Kemper]

The same problem exists in the "Open" dialog. Command-. works in I.E. and other
apps, but not Chimera.

Command-. does work in the "Print" dialog. By all means, disable the "Stop
Loading" shortcut when another panel is frontmost. Command-. should apply to the
current panel, as it does in the "Print" panel.

Comment 5

[Ludovic Hirlimann [:Usul]]

True for the Open dialog in 2003082402. others not tested.

Comment 6

[Gabriel Radic]

This is new, I always thought Command+. should stop an action in progress, like
loading a page - this works, BTW. I like it, anyway, and I plan to use it.

In Camino, it works in the Print and Page Setup dialog, but not for 
- Open
- Save As
- Add Bookmark

Shouldn't this be a system-wide thing that just works? 

Comment 7

[Stuart Morgan]

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

Comment 8

[Stuart Morgan]

Also broken in about and prefs

Comment 9

[Simon Fraser [no longer active]]

Does this work in any cocoa apps?

Comment 10

[Jasper]

Yes, almost all apple apps have this feature.

Comment 11

[philippe (part-time)]

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

Comment 12

[Joel Siegel]

(In reply to comment #2)
> This is because Command-. is used by the menu. According to Apple's docs,
> Command-key shortcuts don't percolate up the responder chain like most events,
> but drip down the view hierarchy.
> 
> I'd say this is by design, but one workaround would be to disable the "Stop
> Loading" shortcut when a panel is frontmost.

AFAIK, other browsers, e.g. FF, manage to do both without problems.  Just confirmed this behavior in FF.

Comment 13

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

Mass un-setting milestone per 1.6 roadmap.

Filter on RemoveRedonkulousBuglist to remove bugspam.

Developers: if you have a patch in hand for one of these bugs, you may pull the bug back to 1.6 *at that point*.

Comment 14

[Chris Peterson [:cpeterson]]

Does this bug only happen in older releases of Mac OS X? I am running Mac OS X 10.6.4 and Command-. WORKSFORME on all versions of Camino I have tested: Camino 1.0.6, 1.5.5, 1.6.11, 2.0.4, and 2.1a1pre.

Comment 15

[Chris Lawson (gone)]

Based on when it was last updated, I'm guessing 10.3 was probably the last OS this was tested on. I can test on 10.4 later but I know Smokey's on 10.5 and can test there. If it works on 10.4+, I think it's safe to WORKSFORME it.

Comment 16

[philippe (part-time)]

That works fine on 10.5/intel with 2.0.4 and recent nightly builds.

Comment 17

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

(In reply to comment #15)
> I can test on 10.4 later but I know Smokey's on 10.5 and
> can test there. If it works on 10.4+, I think it's safe to WORKSFORME it.

And if it doesn't work on 10.4, we should just "[10.4]" the summary and leave it open until we drop 10.4 support.