当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

"Search for text" Zooms when number keys pressed. Expecting it to FIND text

  • 4 件の返信
  • 1 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: FredMcD

more options

For months I have been using (&relying on) the "search for text when I start typing " feature. I am a school teacher & this helps me to search for students & record scores in an online grading program.

The "search for text when I start typing feature" stopped working two days ago. Before, whenever I typed the "Find" box immediately opened up, searched the screen,

and highlighted whatever I had just typed.  Now, when I enter a "1", "2" , "6" , "9" or "0" (zero) 

the find box does not come up- so this disrupts all the grade recording process for me.

Instead, when I type in 6 or 9 (it zooms in the screen instead), 0 (it zooms out instead) and I cannot tell what happens when I type in 1 or 2 (nothing appears to happen- but no "Find" box comes up.


Edit by a moderator to improve the title (As suggested by a contributor, flagging the post) Was

  • The Firefox "search for text when I start typing feature" has just stopped working correctly

Now

  • "Search for text" Zooms when number keys pressed. Expecting it to FIND text

~J99


I tried restarting Firefox and turning on/off the Advanced feature ( "search for text when I start typing feature") but it did not help. I am using a Mac. I also tried using an external keyboard/keypad but the exact same results occur.

Please help!

Thanks, Barry

For months I have been using (&relying on) the "search for text when I start typing " feature. I am a school teacher & this helps me to search for students & record scores in an online grading program. The "search for text when I start typing feature" stopped working two days ago. Before, whenever I typed the "Find" box immediately opened up, searched the screen, and highlighted whatever I had just typed. Now, when I enter a "1", "2" , "6" , "9" or "0" (zero) the find box does not come up- so this disrupts all the grade recording process for me. Instead, when I type in 6 or 9 (it zooms in the screen instead), 0 (it zooms out instead) and I cannot tell what happens when I type in 1 or 2 (nothing appears to happen- but no "Find" box comes up. -------- Edit by a moderator to improve the title (As suggested by a contributor, flagging the post) Was *The Firefox "search for text when I start typing feature" has just stopped working correctly Now *"Search for text" Zooms when number keys pressed. Expecting it to FIND text ~J99 I tried restarting Firefox and turning on/off the Advanced feature ( "search for text when I start typing feature") but it did not help. I am using a Mac. I also tried using an external keyboard/keypad but the exact same results occur. Please help! Thanks, Barry

この投稿は John99 により に変更されました

すべての返信 (4)

more options

The keyboard shortcut for resetting the zoom level is Command+0, so seeing that kind of response implies that Firefox is misreading the state of the Command key, thinking it is stuck down. Usually tapping the key numerous times will send a signal to all programs that the key has been released (at least on Windows).

On the other hand, in that case, Command+6 should jump to the sixth tab in the current window, it shouldn't change the zoom level. So... hmm...

In case a component of the OS has malfunctioned, have you already tried shutting down the system completely and then starting it up again?

この投稿は jscher2000 - Support Volunteer により に変更されました

more options

You may have turned on caret browsing <F7> by accident. Caret Out {web link} Disables change of the caret browse mode by shortcut key(F7).

more options

Did you close and restart Firefox or possibly reboot the computer?

I'm not sure if the Num Lock state can effect this behavior, so maybe check that.

more options

Is your <Num Lock> turned on?