搜索 | 用户支持

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

详细了解

No Resize or Stop on New Awesome Bar

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

more options

I just upgraded to FF4 and my Awesome Bar does not have the Resize or Stop button attached on the right side as the New Features page suggests it would. I would love to use that feature, how do I enable it?

I just upgraded to FF4 and my Awesome Bar does not have the Resize or Stop button attached on the right side as the New Features page suggests it would. I would love to use that feature, how do I enable it?

被采纳的解决方案

  • Make sure that the "Navigation Toolbar" and the "Bookmarks Toolbar" are visible: "View > Toolbars"
  • If items are missing then open the Customize window via "View > Toolbars > Customize" or via "Firefox > Options > Toolbar Layout"
  • If a missing item is in the toolbar palette then drag it back from the Customize window on the toolbar
  • If you do not see that item then click the "Restore Default Set" button to restore the default toolbar set up

See also:

定位到答案原位置 👍 4

所有回复 (3)

more options

The Reload and Stop button occupy the same space in the Location bar as the green Go button does. Go appears when you start typing, the Stop button appears there while the page is loading, and the Reload button appears when the page is fully loaded.

If that is not happening, you might have an extension installed that is causing that issue.

http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes

more options

选择的解决方案

  • Make sure that the "Navigation Toolbar" and the "Bookmarks Toolbar" are visible: "View > Toolbars"
  • If items are missing then open the Customize window via "View > Toolbars > Customize" or via "Firefox > Options > Toolbar Layout"
  • If a missing item is in the toolbar palette then drag it back from the Customize window on the toolbar
  • If you do not see that item then click the "Restore Default Set" button to restore the default toolbar set up

See also:

more options

Turns out it was a corrupt local-store. Resetting it took care of the problem.

Thanks to both cor-el and the-edmeister for their help!

M