Closed
Bug 1138466
Opened 11 years ago
Closed 11 years ago
Keyboard Stopped working
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1137229
People
(Reporter: agustinpetruccelli, Unassigned, NeedInfo)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150302004030
Steps to reproduce:
I couldn´t find Firefox DeleloperEdition as a product, so I posted the bug here. Right now I´m using the version 38.0a2 but this problem happens since a week or ten days ago. My computer is a Macbook Pro 13" with OXS 10.8.5
It´s dificult to reproduce because it´s appear to be a random error.
Actual results:
I´m using normally the browser and suddenly the keyboard stop working. This happens 4 or 5 times per day and I have to restart Firefox. I can use the mouse and navigate, but I can´t type anything anywhere. I can´t write an email, complete a form or even type an URL in the navigation bar, nothing.
Expected results:
I expect to use the keyboard while I´m using your software...
Comment 1•11 years ago
|
||
Can you try opening a new window (File menu) using the mouse next time this happens
and let us know if keyboard input works in that window? Thanks.
Comment 2•11 years ago
|
||
Additional questions: if you click on the URL bar when the keyboard problem occurs,
do you see a blinking caret? is the URL bar highlighted with a focus outline?
Comment 3•11 years ago
|
||
Masayuki-san, could the problem be caused by IME? it sounds like the problem is some
global state that's wrong somehow. Is it possible to disable IME for testing purposes?
Severity: normal → major
Component: General → Event Handling
Flags: needinfo?(masayuki)
Keywords: regression
Product: Firefox → Core
Version: Firefox 38 → 38 Branch
| Reporter | ||
Comment 4•11 years ago
|
||
(In reply to Mats Palmgren (:mats) from comment #1)
> Can you try opening a new window (File menu) using the mouse next time this
> happens
> and let us know if keyboard input works in that window? Thanks.
Good idea, if I open a new window it works fine.
| Reporter | ||
Comment 5•11 years ago
|
||
(In reply to Mats Palmgren (:mats) from comment #2)
> Additional questions: if you click on the URL bar when the keyboard problem
> occurs,
> do you see a blinking caret? is the URL bar highlighted with a focus outline?
It´s normal. The caret blinking and everything is normal. No difference between the error window and the new window were it works.
Bye!
Comment 6•11 years ago
|
||
[Tracking Requested - why for this release]:
Rather horrible regression
tracking-firefox39:
--- → ?
Comment 7•11 years ago
|
||
Possible dupe of bug 1137229.
I'm seeing this too, so I did a quick search on bugs mentioning "keyboard" since the beginning of February.
Comment 8•11 years ago
|
||
(In reply to Mats Palmgren (:mats) from comment #3)
> Masayuki-san, could the problem be caused by IME? it sounds like the problem
> is some
> global state that's wrong somehow.
I'm not sure.
On Mac OS X, we do just not call super view's interpretKeyEvents while IME is disabled (i.e., while nobody doesn't have focus or a non-editable element has focus like button).
http://mxr.mozilla.org/mozilla-central/source/widget/cocoa/TextInputHandler.mm?rev=50b89dc93750#1582
Even if we don't call it, insertText must be called because we need to dispatch keypress event and it's dispatched from insertText if the key is a printable key.
http://mxr.mozilla.org/mozilla-central/source/widget/cocoa/TextInputHandler.mm?rev=50b89dc93750#2139
This will be handled as shortcut key like Command + C.
> Is it possible to disable IME for
> testing purposes?
No way. However, reporter can log the behavior with NSPR_LOG_FILE=~/fx.log NSPR_LOG_MODULES=TextInputHandlerWidgets:5.
Note that don't post the log file without trimming key event logs caused by your usual usage because it may include your sensitive information like passwords. Please post only the logs some key presses which is tested intentionally after this bug is reproduced.
Flags: needinfo?(masayuki)
Comment 9•11 years ago
|
||
[Tracking Requested - why for this release]:
Tracking this since it sounds like a bad regression. If we dupe it to bug 1137229 please nominate it for tracking there.
Comment 10•11 years ago
|
||
I am seeing this behavior also in beta 37 on OSX Yosemite. I notice it when NoScript extension is active. Haven't noticed with other extensions but could be...
Keyboard stops accepting inputs anywhere in Firefox - address bar, fields, etc. -- but works normally in other apps. Focusing on other apps then returning to Firefox doesn't help. Only thing that works is a restart of Firefox.
Comment 11•11 years ago
|
||
I don't have NoScript, but I assume pasting about:support data would be helpful, so here's mine: https://pastebin.mozilla.org/8825003
Comment 12•11 years ago
|
||
Tracking 37+ on both reported bugs at this point.
Comment 13•11 years ago
|
||
Whoever sees this bug, please test with builds dated 2014-02-20 and earlier -- especially m-c and Developer Edition nightlies. Be sure to test with e10s mode off.
Those builds don't contain my patch for bug 1110888.
Comment 14•11 years ago
|
||
Updating my prior comment (10) to note that the issue occurs even without NoScript installed.
Opening a new window does fix the problem in the new window -- but not in the original window.
Comment 15•11 years ago
|
||
Here's the opt tryserver build from bug 1137229 comment #27:
http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/smichaud@pobox.com-7f8185f65f28/try-macosx64/firefox-39.0a1.en-US.mac.dmg
Whoever sees this bug please test with it (until the patch for bug 1137229 lands on mozilla-central).
Comment 16•11 years ago
|
||
The patch for bug 1137229 is in today's mozilla-central nightly.
Whoever sees this bug, please test with it.
Comment 17•11 years ago
|
||
Can you still reproduce with the latest Firefox Developer Edition?
Flags: needinfo?(agustinpetruccelli)
Comment 18•11 years ago
|
||
I'm marking this as a dup of bug 1137229 but, given the severity of the issue, I'm going to keep the tracking and status flags in case this is not a dup and needs to be reopened.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•7 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•