Make it clearer that the onbeforeunload dialog can be ignored by attempting to close the tab again

NEW
Unassigned

Status

()

enhancement
4 years ago
4 years ago

People

(Reporter: jruderman, Unassigned)

Tracking

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [Fitts's law])

Reporter

Description

4 years ago
Now that bug 1050638 is fixed, it's possible to close the onbeforeunload dialog by attempting to abandon the page again. But this isn't obvious, and most users will go the slower route of clicking the 'Close' button in the dialog instead, because it looks like a modal dialog.

I suggest removing the 'Leave page' button and adding the following text:
  <Action> again to close this <tab or window>

where <Action> is whatever the user did to close the page:
  Press ⌘W
  Press ⌘⇧W
  Click the close-tab button
  Click the close-window button

We could also remove the 'Stay on page' button and just make the message disappear after a few seconds, similar to the full-screen warning.
Reporter

Updated

4 years ago
Whiteboard: [Fitts's law]

Comment 1

4 years ago
(In reply to Jesse Ruderman from comment #0)
> I suggest removing the 'Leave page' button and adding the following text:
>   <Action> again to close this <tab or window>
> 
> where <Action> is whatever the user did to close the page:
>   Press ⌘W
>   Press ⌘⇧W
>   Click the close-tab button
>   Click the close-window button
> 
> We could also remove the 'Stay on page' button and just make the message
> disappear after a few seconds, similar to the full-screen warning.

The combination of these two suggestions would probably lead to user confusion as to why the suggested repeating of their action doesn't work if they only do it after the message disappears, though...
Reporter

Comment 2

4 years ago
Well, we could make it work even after the message disappears. If the user hasn't interacted with the page in any other way since pressing ⌘W the first time (cf bug 636905), and fewer than 30 seconds have passed.
You need to log in before you can comment on or make changes to this bug.