搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

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. :)

有帮助吗?

我要提问

您需要登录才能回复。如果您还没账号,可以提出新问题