Risposte recenti a Why did my keyboard shortcut stop working with the latest version of Firefox?https://support.mozilla.org/it/questions/12690142019-09-23T07:42:26-07:00Is there anyone who can update the scripts for your CMS? If so, they can review the developer inform2019-09-23T07:42:26-07:00jscher2000https://support.mozilla.org/it/questions/1269014#answer-1254450<p>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.
</p>Thank you, JSCHER2000 for your response.
This started becoming an issue just recently - I don't kn2019-09-23T04:00:43-07:00bcalzadahttps://support.mozilla.org/it/questions/1269014#answer-1254415<p>Thank you, JSCHER2000 for your response.
</p><p>This started becoming an issue just recently - I don't know exactly when though.
</p><p>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.
</p><p>I guess my question is: Is this not going to work anymore, no matter what key combination is pressed, with Firefox?
</p><p>I opened the links you sent, thank you.
</p><p>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.
</p><p>Thank you again for help in finding a resolution for this!
</p>Hi bcalzada, do you recall the last time this worked normally and when it changed?
Firefox 65 change2019-09-17T10:10:28-07:00jscher2000https://support.mozilla.org/it/questions/1269014#answer-1252910<p>Hi bcalzada, do you recall the last time this worked normally and when it changed?
</p><p>Firefox 65 changed how sites receive certain keyboard events, so if the problem started in or after Firefox 65, you could suggest trying this:
</p><p>(1) In a new tab, type or paste <strong>about:config</strong> in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.
</p><p>(2) In the search box above the list, type or paste <strong>hack</strong> and pause while the list is filtered
</p><p>(3) Double-click the <strong>dom.keyboardevent.keypress.hack.dispatch_non_printable_keys.addl</strong> preference to display a dialog where you can list sites that should have the old behavior and enter the host name, then click OK
</p><p>So for example, if the site address was <a href="https://webapp.example.com/" rel="nofollow">https://webapp.example.com/</a> you would enter just the hostname portion
</p><pre>webapp.example<em>.</em>com
</pre>
<p>If you need to list more than one host name, separate them with commas but no spaces.
</p><p>If you try it, does it make any difference?
</p><p><em><strong>=== Developer Info ===</strong></em>
</p><p>Scripts can still intercept keydown and keyup events for non-printing keys, but not keypress. See:
</p>
<ul><li> <a href="https://www.fxsitecompat.dev/en-CA/docs/2018/non-printable-keys-no-longer-fire-keypress-event/" rel="nofollow">https://www.fxsitecompat.dev/en-CA/docs/2018/non-printable-keys-no-longer-fire-keypress-event/</a>
</li><li> Examples: <a href="https://www.jeffersonscher.com/res/keyvents.html" rel="nofollow">https://www.jeffersonscher.com/res/keyvents.html</a>
</li></ul>