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

搜索 | 用户支持

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

详细了解

Firefox patches really need to stop forcing UI changes on users

  • 1 个回答
  • 2 人有此问题
  • 2 次查看
  • 最后回复者为 the-edmeister

more options

Everytime Firefox makes a UI change, it forces the change on users and then people have to spend time figuring out how to reverse the change. This really should not be happening (imagine how annoying it would be if Microsoft kept changing the windows UI without even telling you what it just did). If a patch changes the UI by adding new buttons or whatever, the patch should tell users what it is exactly and allow them to choose whether to allow the change or stick with their current UI.

Right now the patch installation process basically goes "hey we upgraded your firefox. no, we wont tell you what we did exactly or how to change it, go figure it out yourself" which is really annoying.

Everytime Firefox makes a UI change, it forces the change on users and then people have to spend time figuring out how to reverse the change. This really should not be happening (imagine how annoying it would be if Microsoft kept changing the windows UI without even telling you what it just did). If a patch changes the UI by adding new buttons or whatever, the patch should tell users what it is exactly and allow them to choose whether to allow the change or stick with their current UI. Right now the patch installation process basically goes "hey we upgraded your firefox. no, we wont tell you what we did exactly or how to change it, go figure it out yourself" which is really annoying.

所有回复 (1)

more options

Specifically, what was changed?

There was a change made to search engines to revert or stop malware from substituting their own search engine in place of the search engines that come with Firefox; I lost 2 custom search engines that had the same "short name" as the default search engines. But that's all I saw with the Firefox 40 update. And I have seen some users post about "lost" toolbar buttons - but their was a bit of confusion which may have been related to "signing" of extensions ...