We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Error Sound When Typing

  • 4 回覆
  • 1 有這個問題
  • 5 次檢視
  • 最近回覆由 eugbug1

more options

This may be me nudging the mouse with the side of my arm causing loss of focus up to the menu, but when I type in the URL bar or elsewhere, I'm getting a warning tone as though characters aren't being recognised. It only seems to happen in the browser, not other applications. Also in Facebook, the cursor disappears sometimes when I click in the comment panel, but characters still appear as I type. I have to close the comment editor and reopen to make the cursor appear.

This may be me nudging the mouse with the side of my arm causing loss of focus up to the menu, but when I type in the URL bar or elsewhere, I'm getting a warning tone as though characters aren't being recognised. It only seems to happen in the browser, not other applications. Also in Facebook, the cursor disappears sometimes when I click in the comment panel, but characters still appear as I type. I have to close the comment editor and reopen to make the cursor appear.

所有回覆 (4)

more options

The warning sound is from Windows presumably. This doesn't happen for every character, only sometimes. It doesn't happen with other applications.

more options

I cleared the cache and deleted the Firefox cookie, but this didn't help. The problem only happens when typing the first character in a panel on any website (not just the URL bar). It always seems to be the first character that's rejected as though there's a delay recognising it. Then when that key is typed again, it keeps working.

more options

I've eliminated the possibility of loss of focus due to inadvertently moving the mouse cursor to the menu bar or taskbar. The issue still happens without doing this.

more options

The latest version, 111.0 64 bit appears to have fixed this bug.