-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot type anything in Firefox nightly #217
Comments
It's perfect!
Ryan
…On Wed, Mar 27, 2019, at 05:54, Geoffrey Thomas wrote:
On Firefox nightly 68.0a1 (2019-03-22) on Debian stable, I can't type
anything other than the Enter key.
@alex <https://github.com/alex> suggested I try setting the preference
dom.keyboardevent.keypress.hack.use_legacy_keycode_and_charcode to
include pypyjs.org, and that fixed it and I can type normally.
Presumably there's some non-legacy thing PyPyJS needs to do.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#217>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACHhxq0WsMS5PXgKvBAUMt5701LJKEPks5vamz4gaJpZM4cMNbN>.
|
Well that's embarassing, looks like I email replied to this github issue rather than to an unrelated email. Sorry about that. |
Thanks for reporting this, but I have to be honest, I don't expect to make time to dig into this issue at all. |
Just so you know, same problem and (hacky) solution on Ubuntu 18.04 LTS firefox. |
This still exists on Ubuntu LTS 22.04 / Firefox 106 and will presumably do so forever - the explanation is here - https://support.mozilla.org/en-US/kb/dom-events-changes-introduced-firefox-66 The work around remains
Thanks for leaving this up so that it can be experimented with. |
On Firefox nightly 68.0a1 (2019-03-22) on Debian stable, I can't type anything other than the Enter key.
@alex suggested I try setting the preference dom.keyboardevent.keypress.hack.use_legacy_keycode_and_charcode to include pypyjs.org, and that fixed it and I can type normally. Presumably there's some non-legacy thing PyPyJS needs to do.
The text was updated successfully, but these errors were encountered: