1044718 - Unable to dismiss "Do you want to replace it?" in save dialog with escape key

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[gnoise]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 (Beta/Release)
Build ID: 20140722195627

Steps to reproduce:

Save any file over an existing file, forcing Firefox to ask you if you wish to overwrite the file.

A message box appears asking you to confirm if you want to overwrite or not.
Screenshot: http://i.imgur.com/n3EQ5pS.png

Tested on Windows 7 and Windows 8.1.


Actual results:

This question can not be dismissed (answering "No") by pressing escape.
You can press space, "n" or enter to dismiss, however the also very common way to dismiss, with escape, is not doing anything.


Expected results:

The escape key should answer "No" and cancel the operation.

Comment 1

[matcheydj]

According to the guys who make Windows, "If the dialog box displays a Cancel button, pressing the ESC key has the same effect as clicking Cancel." This might not extend to the "No" option, weird as it sounds.

This could be due to the way Firefox developers have coded the file confirmation dialog itself, since key behavior can be set any way they decide. ESC is now common in browsers for cancelling full-screen mode, for example. To be sure, I would suggest checking your Firefox settings for any hotkeys that contain the ESC key.

Comment 2

[Jan Henning [:JanH]]

It happens on a fresh Firefox profile as well.

However I've tested a number of other programs on my computer, and all programs that use the standard Windows save file dialog exhibit the same behaviour as that observed in Firefox, so I'd guess that it's rather a Windows than a Firefox problem.

Comment 3

[:Gijs (he/him)]

(In reply to JanH from comment #2)
> It happens on a fresh Firefox profile as well.
> 
> However I've tested a number of other programs on my computer, and all
> programs that use the standard Windows save file dialog exhibit the same
> behaviour as that observed in Firefox, so I'd guess that it's rather a
> Windows than a Firefox problem.

Indeed.