Closed Bug 675782 Opened 13 years ago Closed 5 years ago

Keyboard shortcuts don't work in error page

Categories

(Firefox :: General, defect)

4.0 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: brille1, Unassigned)

Details

(Whiteboard: [testday-20110805])

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
Build ID: 20110318052756

Steps to reproduce:

I was unsuccessfully trying to ...

a) open a new tab using CTRL+T,
b) repeat the failed request using RETURN

while the FF error page was displayed.


Actual results:

If FF displays the error page (server timeout, network error, etc.), acceleration keys don't work.

Neither does RETURN trigger a retry nor does CTRL+T open a new tab after clicking the "Retry Request" button of the FF error page.


Expected results:

a) ENTER/RETURN keys should trigger a request retry.

b) CTRL+T should always open a new tab, even after the "Retry Request" button of the FF error page has been pressed.
Does it happen also in Firefox Safe mode?
https://support.mozilla.com/en-US/kb/Safe%20Mode
Whiteboard: [testday-20110805]
Yepp!

Can you reproduce the issue? (Should be easy: Just enter a non-existing domain name. When the error page comes up, hit [ENTER] - unsuccessfully. Then, after you have CLICKED the "Reload page" button, press CRTR+T while the "Reload page" button is disabled, unsuccessfully again.)
No. Can't reproduce even with those steps. Why do you expect Enter to do anything? Where is that defined?
It's the only input element on the whole page. I suggest it to be a submit button.

There is no defitition. This issue is a suggestion, not a bug.

But the other issue, not being able to create a new tab while the error page reloads is in fact a bug. Well, from my point of view. I don't know of any definition about that, but I expect a new tab to appear when I hit CTRL+T anytime.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.