Closed Bug 308548 Opened 20 years ago Closed 18 years ago

Access keys stop working after switching pref panes

Categories

(Firefox :: Settings UI, defect)

Product:
Firefox
Component:
Settings UI
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: u60234, Unassigned)

References

Details

(Keywords: access)

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050914 Firefox/1.4 Bug seen on both trunk and branch. Access keys in Options (Preferences) sometimes stop working if I select another pane, and then switch back to the first pane. This happens if the accesskey I want to use on the first pane is also used on the second pane. And it only seem to happen on panes that have previously been displayed in an Options "session". The access keys works OK the first time a pane is shown. Steps to reproduce: 1. Open Options (Preferences) and, if it's not already shown, select the General pane. 2. Change to the Advanced pane. 3. Change back to the General pane. 4. Press Alt+A to put focus in the "Location(s)" field. Actual result: Nothing.
Bug 143065 has been mentioned when referring to this problem in the past, I'm not entirely sure it's related though.
Someome could test with the patch in bug 143065 and see if that fixes this.
Aaron: I merged your patch from bug 143065 to trunk and "made it compile"(tm), and that didn't work (for this bug). However, I think maybe there has been some logic changes to nsEventStateManager since you made that patch, so I'm not sure it proves anything.
This affects one of my extensions that uses the prefwindow. However in that one I don't use the dyanmically loaded prefpanes, all the panes are coded into the main xul file and so no pane switching is necessary to stop accesskeys from working.
*** Bug 330083 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > Aaron: I merged your patch from bug 143065 to trunk and "made it compile"(tm), > and that didn't work (for this bug). however, the work in bug 143065 is still in progress ...
Depends on: 143065
This works for me now after bug 143065 was fixed.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.