Closed Bug 351305 Opened 18 years ago Closed 18 years ago

Access keys not working with 2.0b2

Categories

(Firefox :: Keyboard Navigation, defect)

Product:
Firefox
Component:
Keyboard Navigation
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: eustaquiorangel, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1b2) Gecko/20060821 Firefox/2.0b2 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1b2) Gecko/20060821 Firefox/2.0b2 The access keys are not working with 2.0b2. I upgraded last Friday and they are gone. Reproducible: Always Steps to Reproduce: 1. Create, for example, a "a href" with the accesskey, firing a JavaScript function. 2. Press the access key. 3. Check if the key pressing did what was expected on the link. Actual Results: Nothing. Expected Results: The press of the key fire the JavaScript function.
Forgot to say: that code works with Seamonkey and the previous Firefox version.
Access keys changed in 2.0, try also with shift. ie: Ctrl+shift+s, instead of Ctrl+s. There is a link explaining how to return to the original behavior, but I can't find it right now.
To revert to the prior behavior, go to about:config and set ui.key.generalAccessKey to 17 (or ui.key.contentAccess to 2). See also bug 349716 for the Windows version of what this bug might be (content accesskeys now require Ctrl+Shift).
I tried here and it worked (with the code provided on the URL) with Alt+Shift+O and Alt+Shift+T. This will be the official behaviour of 2.0 and above? If so, I need to change some texts about how to use the shortcuts.
(In reply to comment #4) > This will be the official behaviour of 2.0 and above? That depends on how bug 349716 will be resolved. Currently it is indeed intended to become the official behavior - but you better wait with modifying any documentation until RC1 or even the final version are released.
Ok, thanks for all your answers! I'm surprised I could not find bug 349716 today when searching, sorry for open this one here.
(In reply to comment #6) No worries.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.