488809 - Add optional splash screen for termination to avoid user's misperception

Status: NEW

(Core :: General, enhancement)

Description

[WADA:World Anti-bad-Duping Agency]

Please add optional splash screen for termination, in order to avoid user's misperception.

Currently, Fx/Tb closes main window just after click of "X" button. And, on MS Win,  Fb/Tb disappears immediately from Task Bar. So, user easily misunderstands that Fx/Tb has terminated completely.

"X" button had been similar to CTRL+ALT+DEL of MS DOS for long time.
But, recent "X" button is similar to CTRL+ALT+DEL of MS Win-NT/2K/XP/Vista/7 or other modern/sophisticated OS'es.
I think a way to let user know about "termination is in progress" is required.

Comment 1

[WADA:World Anti-bad-Duping Agency]

Note: This bug is spin-off of bug 407981 comment #12 and bug 407981 comment #67.

Comment 2

[fcp]

I oppose to this.  Some users wait after they click the X button until the window disappears before they start other tasks (not related to Firefox) because they do not know they do not have to wait.  From the perspective of those users, showing a “shutting down” dialog box slows down the shutdown significantly.

In my opinion, bug 407981 should be solved by improving the “Firefox is already running” dialog box.

The original suggestion says “optional” screen, but I cannot understand what an optional shutting-down dialog box could achieve.  If the default is off, it would hardly avoid misconception.  If the default is on, my point still holds.

Comment 3

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #2)
> From the perspective of those users, showing a “shutting down” dialog box slows down the shutdown significantly.

You are right. "Slowness of shutdown" is exposed to all users by splash screen. Exposed not only to users who click short-cut of Firefox just after click of "X" button. 

> In my opinion, bug 407981 should be solved by improving the "Firefox is already
> running”dialog box.

Bug 407981 itself is mainly for "real long termination time".
If bug 407981 can keep time from "click of X" to "end of process(close of DDE interface, erase of parent.lock, end of firefox.exe)" within one second ALWAYS, "Firefox is already running" almost never occurs. Bug 407981 simply reduces frequency of repeated bug open at open of B.M.O bug of "Firefox is already running". I think "keeping within one second always" is impossible. However, I believe Bug 407981 will reduce the frequency much.

I agree with you on that improvement of "Firefox is already running”dialog is a solution, and it may be better than this bug's proposal for developer.
If already running Tb returns "termination is in progress to DDE request", and if newly started firefox.exe displays "termination is in progress. please wait for ...", bug won't be opened repeatedly. 
It's sibling of Bug 459638(confusing dialog when multiple profile is used).

> If the default is on, my point still holds.

It's problem for developer, not for user. (slowness is exposed to all users).
My "optional" means "user can disable termination splash screen", as "startup splash screen" could be disabled when "startup splash screen" was used because of long startup time.

Comment 4

[WADA:World Anti-bad-Duping Agency]

Oh, "users" you are talking was ordinal/major users who don't(or never) click Firefox's short-cut just after click "X" button of Firefox, who usually do other task than Firefox after click "X" button of Firefox.
For such ordinal/major users, window close just after click "X" button is preferable behaviour(may be mandatory), because many of them wait for complete termination of Firefox for safety, if splash screen by this bug's proposal will be implemented.
I absolutely agree with you on next, if possible.
  If splash screen or dialog of "termination is in progress, wait for a few
  minutes, please" will be displayed, it should be limited to "when short-cut of
  Firefox is clicked again before termination of Firefox completes".

Comment 5

[WADA:World Anti-bad-Duping Agency]

If proposal of Comment #2 by fcp will be implemented, Bug 459638 will be automatically resolved.

Comment 6

[WADA:World Anti-bad-Duping Agency]

Bug 399108 is for similar requet. xref to it.