搜尋 Mozilla 技術支援網站

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

了解更多

Clicks on certain links near the bottom are ignored because of floating status indicator

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

more options

When I try to click on certain links near the bottom of a web page--actually, a customized Bugzilla web page--Firefox 4 does not respond. If I wiggle the mouse enough to make that floating URL "tooltip" (which displays the URL corresponding to the link over which the mouse is hovering) move to the other side of the window and then click on the link, all's well. It's as though that floating URL tooltip is blocking the mouse click.

When I try to click on certain links near the bottom of a web page--actually, a customized Bugzilla web page--Firefox 4 does not respond. If I wiggle the mouse enough to make that floating URL "tooltip" (which displays the URL corresponding to the link over which the mouse is hovering) move to the other side of the window and then click on the link, all's well. It's as though that floating URL tooltip is blocking the mouse click.

所有回覆 (4)

more options

Try to make the Add-ons bar visible (Ctrl /) to see if that helps.

  • View > Toolbars > Add-ons Bar

Press F10 or tap the Alt key to bring up the "Menu Bar" temporarily.

more options

The add-ons bar is already visible. Bringing up the Menu Bar temporarily does not change the behavior.

Neither of those are the tooltip I was referring to. I'm attaching a screen grab which shows my mouse hovering over the link I want to click, and the URL tooltip directly below. If I wiggle enough to make that tooltip move to the other side of the window, I can click on the link. Otherwise, my click is ignored.

more options

Probably the only thing that helps is to have the horizontal scroll bar visible all the time.

Add code to userContent.css or use Stylish


body {overflow-x: scroll !important; }
more options

...I guess you just need to wait a few days for a surprise major release for these kinds of things!

Downloaded 5.0 and the problem no longer occurs.

Thanks!