Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Why did my keyboard shortcut stop working with the latest version of Firefox?

Hello and thanks in advance for your help!

For many years, the content management system that I have been using has worked just fine with previous versions of Firefox. To access the backend area for a client of mine to edit their own website I built for them, they would go to their website and hit Control-Y on any page of their website. This would bring up the login prompt window so they could login and start live editing their site. Now, when I hit Control-Y, nothing happens.

I saw a previous post that mentioned adjusting (allowing) keyboard shortcuts in the settings area. I did this but unfortunately, this didn't solve my issue.

Can someone tell me why this no longer works with Firefox and what the possible fix / workaround might be?

Thank you so much!!

Hello and thanks in advance for your help! For many years, the content management system that I have been using has worked just fine with previous versions of Firefox. To access the backend area for a client of mine to edit their own website I built for them, they would go to their website and hit Control-Y on any page of their website. This would bring up the login prompt window so they could login and start live editing their site. Now, when I hit Control-Y, nothing happens. I saw a previous post that mentioned adjusting (allowing) keyboard shortcuts in the settings area. I did this but unfortunately, this didn't solve my issue. Can someone tell me why this no longer works with Firefox and what the possible fix / workaround might be? Thank you so much!!

All Replies (3)

Hi bcalzada, do you recall the last time this worked normally and when it changed?

Firefox 65 changed how sites receive certain keyboard events, so if the problem started in or after Firefox 65, you could suggest trying this:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.

(2) In the search box above the list, type or paste hack and pause while the list is filtered

(3) Double-click the dom.keyboardevent.keypress.hack.dispatch_non_printable_keys.addl preference to display a dialog where you can list sites that should have the old behavior and enter the host name, then click OK

So for example, if the site address was https://webapp.example.com/ you would enter just the hostname portion

webapp.example.com

If you need to list more than one host name, separate them with commas but no spaces.

If you try it, does it make any difference?

=== Developer Info ===

Scripts can still intercept keydown and keyup events for non-printing keys, but not keypress. See:

jscher2000 - Support Volunteer மூலமாக திருத்தப்பட்டது

Thank you, JSCHER2000 for your response.

This started becoming an issue just recently - I don't know exactly when though.

It looks like you provided a possible workaround or way to force it to work on my computer by going into the about:config area. I can try that and see if it works for one of my client sites but the problem is, I have thousands of clients who use this CMS and many of them use Firefox. Now, none of them can hit Control-Y on their keyboard anymore with Firefox to prompt them to enter their login to start editing their website content. I can't expect these folks to all go into their about:config areas to do this - it will be too difficult/complicated for most.

I guess my question is: Is this not going to work anymore, no matter what key combination is pressed, with Firefox?

I opened the links you sent, thank you.

So, on the Non-Printable Keys article... Is it saying that the script that calls my CMS needs to be modified to no longer use the Keypress for Control-Y but instead Keydown? I'm not a coder so this is a little difficult to follow.

Thank you again for help in finding a resolution for this!

Is there anyone who can update the scripts for your CMS? If so, they can review the developer information and post any follow-up questions. I don't know whether to give you a general example... if the site is publicly accessible, a volunteer could take a look at it.