为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

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

详细了解

autoselecting of text in adressbar and searchbar fails, or happens when I press bacspace

  • 3 个回答
  • 1 人有此问题
  • 6 次查看
  • 最后回复者为 bartjunk64

more options

I just updated from 32.x to 33.1 I'm on win7-64.

I now have a problem whenever I try to access the adress-bar (the control where you type the URL) and the serach-bar. It used to be that when the control did not have focus and you clicked in it, the text was autoselected, this means that when you start typing it replaces the previous text. This behaviour was consistent with other mainstream browsers (IE, Chrome, Opera).

After the update whenever I click in the adress-bar (or search-bar) the text is not selected. Sometimes when I move the mouse to the top (not having any mouse-button down) it selects the text. This is annoying, the only consistent way to select the text now is pressing Ctrl+A. What is even worse, is the fact that when I click in the adress-bar (and search-bar),(no text ets selected), and I press BackSpace button (I'm at end of text) it then selects the text and deletes the entire text.

Along with the fact that typing in FF 33.1 ismuch, much, much slower than in 32, this makes the browser almost completely useless to me, which is a pity, since I'm using FF as my default browser from version 1.5.

Does anybody know a fix for this (or should I downgrade (how to?))?

Bart

I just updated from 32.x to 33.1 I'm on win7-64. I now have a problem whenever I try to access the adress-bar (the control where you type the URL) and the serach-bar. It used to be that when the control did not have focus and you clicked in it, the text was autoselected, this means that when you start typing it replaces the previous text. This behaviour was consistent with other mainstream browsers (IE, Chrome, Opera). After the update whenever I click in the adress-bar (or search-bar) the text is not selected. Sometimes when I move the mouse to the top (not having any mouse-button down) it selects the text. This is annoying, the only consistent way to select the text now is pressing Ctrl+A. What is even worse, is the fact that when I click in the adress-bar (and search-bar),(no text ets selected), and I press BackSpace button (I'm at end of text) it then selects the text and deletes the entire text. Along with the fact that typing in FF 33.1 ismuch, much, much slower than in 32, this makes the browser almost completely useless to me, which is a pity, since I'm using FF as my default browser from version 1.5. Does anybody know a fix for this (or should I downgrade (how to?))? Bart

被采纳的解决方案

Setting layers.offmainthreadcomposition.enabled to false seems to have resolved this issue. The setting of hardware acceleration has no influence on it.

Both possible solutions were found on this forum, so thanks to the community!

定位到答案原位置 👍 0

所有回复 (3)

more options

I can assure you these are not intentional changes.

The slowness and the strange mouse responses might be related, but this is the first report I've read about them, so I'm not sure what's going on there.


To quickly determine whether this might be a settings issue, you could try this 3-minute experiment:

Create a new Firefox profile

A new profile will have your system-installed plugins (e.g., Flash) and extensions (e.g., security suite toolbars), but no themes, other extensions, or other customizations. It also will have completely fresh settings databases and a fresh cache folder.

Exit Firefox and start up in the Profile Manager using Start > search box, or Run (hold down the Windows key and press R):

firefox.exe -P

Don't delete anything here.

Any time you want to switch profiles, exit Firefox and return to this dialog.

Go ahead and click the Create Profile button, give it a name like Nov13, and skip the option to change the folder location. Then start Firefox in the new profile you created.

Until you go back to the Profile Manager and start up in your regular profile, your desktop shortcut should fire up the new profile.

Does the mouse or keyboard behave any better?

Note: When returning to the Profile Manager, you might be tempted to use the Delete Profile button on your new test profile. But... it's a bit too easy to accidentally delete your "real" profile, so I recommend resisting the temptation. If you do want to clean up later, I suggest making a backup of all your profiles first in case something were to go wrong.


In case old/inconsistent files have accumulated in Firefox's program folder, you can replace the program files without disturbing your settings using this Clean Reinstall procedure:

(1) Download a fresh installer for Firefox 33 from https://www.mozilla.org/firefox/all/ to a convenient location. (Scroll down to your preferred language.)

(2) If applicable, exit out of Firefox or make sure it is fully terminated in Task Manager.

(3) Rename the folder (64-bit Windows folder names)

C:\Program Files (x86)\Mozilla Firefox

to

C:\Program Files (x86)\OldFirefox

(4) Run the installer you downloaded in #1. It should automatically connect to your existing settings.

Any improvement with mouse or keyboard??

Note: Some recently installed plugins may exist only in that OldFirefox folder. If something essential is missing, look in these folders:

  • C:\Program Files (x86)\OldFirefox\Plugins
  • C:\Program Files (x86)\OldFirefox\browser\plugins
more options

Thanks for the answer. Currently I have reverted to 32.0. The upcoming days I cannot test, because I need a stable and non-lagging) browser for my work (over Citrix connection).

Once I have the time I will upgrade (again) to 33.1 and perform some more tests (from the observed behaviour in 33.1 I suspect that the autoselection actually is done, but their is no visual sign of this) and follow your suggestions.

Q: Will creating a new profile "kill" my Citrix ICA Client?

I will report back in a few days.

Bart

more options

选择的解决方案

Setting layers.offmainthreadcomposition.enabled to false seems to have resolved this issue. The setting of hardware acceleration has no influence on it.

Both possible solutions were found on this forum, so thanks to the community!