搜尋 Mozilla 技術支援網站

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

Learn More

Dead keys not working only in a specific profile

  • 1 回覆
  • 0 有這個問題
  • 最近回覆由 Kazuma

more options

Today I noticed that typing characters with accents like á, ã, â, etc. doesn't seem to work at all from firefox, they all end up ignoring the dead key and just typing the letter itself. It can render them just fine and I can paste them from another app normally too, but actually typing them is impossible from firefox.

After trying to troubleshoot, I eventually found out a few things: - iBus is not at fault, since it works in every other app and I even restarted it, but the problem persists - This only happens in my main profile, newly created profiles don't have that problem - The problem still happens on troubleshoot mode (as long as it is my main profile) - Compose key also doesn't work (I don't want to use compose key anyway, because my keyboard has specialized dead keys, but I at least tried it)

I suspect the problem lies in a setting on about:config that's different from newly created profiles, but I have no idea which and Ctrl+F searching this site doesn't show any relevant configuration that might be the culprit.

Today I noticed that typing characters with accents like á, ã, â, etc. doesn't seem to work at all from firefox, they all end up ignoring the dead key and just typing the letter itself. It can render them just fine and I can paste them from another app normally too, but actually typing them is impossible from firefox. After trying to troubleshoot, I eventually found out a few things: - iBus is not at fault, since it works in every other app and I even restarted it, but the problem persists - This only happens in my main profile, newly created profiles don't have that problem - The problem still happens on troubleshoot mode (as long as it is my main profile) - Compose key also doesn't work (I don't want to use compose key anyway, because my keyboard has specialized dead keys, but I at least tried it) I suspect the problem lies in a setting on about:config that's different from newly created profiles, but I have no idea which and Ctrl+F searching [https://kb.mozillazine.org/About:config_entries this site] doesn't show any relevant configuration that might be the culprit.

被選擇的解決方法

It turned out that the problem was the focusmanager.testmode setting set to true because of Flutter or something. Setting it to default (false) solved the problem.

I found this setting was the problem by cloning my profile and repeatedly deleting a bunch of settings in prefs.js, opening the cloned profile with the changes and closing when the problem persisted.

Leaving this short issue here for the next confused person. :)

從原來的回覆中察看解決方案 👍 0

所有回覆 (1)

more options

選擇的解決方法

It turned out that the problem was the focusmanager.testmode setting set to true because of Flutter or something. Setting it to default (false) solved the problem.

I found this setting was the problem by cloning my profile and repeatedly deleting a bunch of settings in prefs.js, opening the cloned profile with the changes and closing when the problem persisted.

Leaving this short issue here for the next confused person. :)

有幫助嗎?

問個問題

如果您還沒有帳號,您必須先登入帳號 來回覆文章。還沒有帳號的話,只能發問新問題