Closed Bug 225182 Opened 21 years ago Closed 21 years ago

Support reopen Apple event

Categories

(Firefox :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 204484

People

(Reporter: manfred, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031109 Firebird/0.7+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031109 Firebird/0.7+

If Firebird is already running in the background without a window open clicking
its Dock icon does not create a new window.



Reproducible: Always

Steps to Reproduce:
1. Close all Firebird windows.
2. Switch to the Finder.
3. Click the Firebird Dock icon.

Actual Results:  
Menubar changes to Firebird but no new window is created.

Expected Results:  
New window should be created for the user.

http://developer.apple.com/technotes/tn/tn1102.html

Reopen Application Apple Event

Finder 8 now sends running applications a reopen application Apple event
(kAEReopenApplication == 'rapp') whenever the user reopens the application. The
purpose of the reopen application Apple event is to allow the application to
provide visual feedback to the user.

User testing has indicated that when a user double-clicks on an application's
icon, or in some other way causes the application to be launched, they expect to
see some visual feedback that the application has in fact started and is ready
for use. This visual feedback is often a new untitled document window or a
document creation dialog when a document file has not been opened. Users
associate this feedback with the action of double-clicking on the application icon.

It was discovered that when users double-clicked on the icon for a running
application, and there was no visual feedback from the application (such as a
document window or tool pallet), they would often think that something was wrong
because nothing happened. Testing showed that the menu bar change (including the
application menu icon) when the running application came to the front was not
enough of a visual clue for novice users. They didn't realize that the
application whose icon they had just opened was in the front ready for their use.

The idea behind sending the reopen application Apple event to the running
application is to let the application know that the user has attempted to open
it. When handling the reopen application Apple event, the application has an
opportunity to provide visual feedback to the user. What the application does
will depend on the application itself, and on the current state of the
application. The action taken should also take into consideration any startup
options the user has set in the preferences for the application.

In general, if no windows are open in the application, the action taken should
be similar to what happens when the open application (kAEOpenApplication ==
'oapp') Apple event is received after the application is launched. This could be
opening an untitled document, or perhaps displaying a document creation dialog.
If the application already has windows open -- be they document, tool pallet,
dialog, etc. -- this will most likely be enough feedback and nothing further
needs to be done.

Application frameworks should provide support for the reopen application Apple
event. In many cases, the framework will be able to leverage the support it
already provides for the open application Apple event. It could, for example,
provide a global flag to indicate that the first Apple event has been handled at
application startup time. After the flag is set, the open application Apple
event handler would behave as the reopen application Apple event handler.

*** This bug has been marked as a duplicate of 204484 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.