Closed Bug 1336141 Opened 4 years ago Closed 4 years ago

Access keys in proxy dialog in preferences no longer work

Categories

(Firefox :: Preferences, defect)

54 Branch
x86_64
All
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1194528
Tracking Status
firefox51 --- wontfix
firefox52 --- wontfix
firefox53 --- wontfix
firefox54 --- fix-optional

People

(Reporter: appa.g0dlike, Unassigned)

References

Details

(Keywords: regression)

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36

Steps to reproduce:

1. Go to about:preferences#advanced
2. Click on the Network tab
3. Click on Settings (under Connection)
4. On the keyboard, enter the key combination Alt+m


Actual results:

Nothing.


Expected results:

When the key combination of Alt+m would be pressed (after Connection Settings dialog opens), the radio button for "Manual proxy configuration" should have been selected.
This goes for other keyboard shortcuts too which would select different options depending on the underlined letter.
Last version where this was working as expected for me was 50.0.2
Keywords: regression
Whiteboard: keyboard shortcuts, settings, preferences
Does this reproduce in Firefox's safe mode and/or a new profile? https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems
Whiteboard: keyboard shortcuts, settings, preferences
Yes, reproduced under safe mode and new profile.
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
I can reproduce this on Windows 10 with FF Nighlty 54.0a1(2017-02-03). I run mozregression and here is the pushlog:
https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=a6f67ab4a4ec4dd66f53c4b4423e5b8b63023388&tochange=dce857dd57e2d91ae4c6014cf21e93ef95e4dd36
Also in mozregression I have a commit message:  Bug 1282910 - Fix issuerOrganizationUnit property name in test_security-info-certificate.js. r=jsnajdr

Mgsudhanva do you have any idea about this? Thanks  

Note: I couldn't reproduce it on Mac 10.10.
Status: UNCONFIRMED → NEW
Component: Untriaged → Preferences
Ever confirmed: true
Flags: needinfo?(mgsudhanva)
OS: Linux → All
Version: 51 Branch → 54 Branch
This is a regression from Joseph Yeh — Bug 1036815 - Convert Advanced pane dialogs to be in-content. r=MattN  not the other bug.
Blocks: 1036815
Flags: needinfo?(MattN+bmo)
Flags: needinfo?(mgsudhanva)
Summary: Keyboard shortcuts in Preferences no longer work. → Access keys in proxy dialog in preferences no longer work
Access keys don't work for me at all in about:preferences (Nightly on Windows 10).
(In reply to AppAraat from comment #0)
> When the key combination of Alt+m would be pressed (after Connection
> Settings dialog opens), the radio button for "Manual proxy configuration"
> should have been selected.
In the new Preferences, you have to press Alt + Shift + <letter>. This is bug 1194528.
Can you test if Alt + Shift + M selects the item you want?

(In reply to Steffen Wilberg from comment #6)
> Access keys don't work for me at all in about:preferences (Nightly on
> Windows 10).
Do you use Alt + Shift + <letter>? Works here on Windows 8.1 + Nightly 54.0a1 20170205030206. Please file a new bug (this one will get closed if that works for the reporter).
Flags: needinfo?(MattN+bmo) → needinfo?(appa.g0dlike)
Right, Alt+Shift+letter works for me in about:preferences, including subdialogs.
(In reply to Sebastian Hengst [:aryx][:archaeopteryx] (needinfo on intermittent or backout) from comment #7)
> Can you test if Alt + Shift + M selects the item you want?

Yes, I can confirm that Alt + Shift + M selects the item I want.
Furthermore, I can confirm that other access keys also work with the Alt + Shift key combination.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1194528
Mark 51 won't fix as there is no plan to ship 51 do release right now.
Also too late to fix in 53. But, I did notice there may be a workaround mentioned in https://bugzilla.mozilla.org/show_bug.cgi?id=1194528#c1 . Hope that helps for now.
You need to log in before you can comment on or make changes to this bug.