Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

Chủ đề này đã đóng và được lưu lại. Vui lòng hỏi một câu hỏi mới nếu bạn cần giúp đỡ.

Changes in Firefox 23 - not for the better

  • 24 trả lời
  • 53 gặp vấn đề này
  • 216 lượt xem
  • Trả lời mới nhất được viết bởi John99

more options

I just got Firefox 23, and found there is no more Enable Javascript checkbox in the Content area of Preferences and there is no more ability to prevent changes to the functioning of the context menu and prevent the changing of the size or position of the window. I really do not understand why certain settings to control what may be done by web page code to the browser are being gutted out. Presumably it means that any smartass who can write a web page can force my browser window to be whatever size he wants it to be. That used to drive me crazy in the past, and it will do the same thing again. Is there any way to make a capability policy that could stop the resizing of the window? I just found out that I can still use the context menu if I use Shift-right-click. Why the change?

Autohiding the tab bar does not work any more. I thought the big argument for trying to put tabs on top and into the title bar was to save space? Forcing the tab bar to be visible all the time will certainly not save space, so why do it?

My bookmark menu was removed from the bookmarks toolbar. I tried to find a button that would put it back, and there are two bookmarks buttons in the customize window. Are the developers trying to make things harder, or what?

Giải pháp được chọn

Tất cả các câu trả lời (20)

more options

Giải pháp được chọn

you can easily hide your Tab bar with https://addons.mozilla.org/en-us/firefox/addon/hide-tab-bar-with-one-tab/, restore the ability to disable Javascript with https://addons.mozilla.org/en-US/firefox/addon/settingsanity/ (among other add-ons)

more options

Thanks. I found that first extension and I am now using it. The second one I do not need as long as the settings that I have already are still working.

I presume that the Mozilla developers want to force the users of Firefox to become more familiar with the settings in about:config, since they seem to be steadily removing settings from the normal user GUI.

I still do not understand why the bookmark button would be removed from my bookmarks toolbar and put back in the customize window. Why change the toolbar layout?

more options

It's unfortunate that these settings are harder to find now. This is the old help article description annotated with my notes:

Advanced JavaScript Settings

Allow scripts to:

  • [X] Move or resize existing windows: Uncheck this option/preference to disable moving and resizing windows using scripts.
    • In about:config: dom.disable_window_move_resize
      (default=false, set to true to block sites)
  • [ ] Raise or lower windows: Uncheck this option/preference to make sure scripts cannot raise (bring to the front) or lower (send to the back) windows.
    • In about:config: dom.disable_window_flip
      (default=true, set to false to allow sites)
  • [X] Disable or replace context menus: Uncheck this option/preference to prevent web pages from disabling or changing the Firefox context menu.
    • In about:config: dom.event.contextmenu.enabled
      (default=true, set to false to block sites)
more options

Hi finitarry refer to

more options

My bookmarks drop-down button was removed from the Bookmarks Toolbar.

At first I thought it was a glitch, since I can't think of a good reason for it.

However, upon placing the button back on the bar I notice its behavior as changed. Previously it would hide itself when the classic menu bar is displayed only when I placed it on the Navigation toolbar. Now it also hides when I place it on the Bookmarks Toolbar.

So either it is a new button, or it was removed because I have the classic menu bar displayed. Or it is a glitch. :-)

more options


I get the point about disabling encryption and images, but the javascript options were useful, so why were they systematically cut out a few at a time? It would be interesting to know when the versions of encryption algorithms change, so where would I find that information now? I can see some reference to TLS in about:config, but I am not sure what those settings mean.


Since I am using Mac OS, I have had the bookmarks menu button on the bookmarks toolbar as well as a bookmarks menu on the normal menu bar, since that one cannot be hidden (hooray!). After I put the bookmarks menu button back on the bookmarks toolbar, it behaves as before and is never hidden.

more options

I just opened an account here to provide feedback on the problems with the new release, but you seem to have covered everything.

Personally, I can't put up with the tab business and don't want add-ons, so I have reverted to version 22, but I'd love to hear if this business is reversed on later versions of Firefox so I can continue to more forward with Mozilla.

more options

I doubt if those changes are going to be reversed. An all new user interface is being developed and this "tab business" is part of the 3rd volley of changes being made in preparation for the new user appearance. If you don't like the way Google Chrome looks, you aren't going to like the new Firefox user interface.

more options

What about the fact that instead of defaulting to a Google search anything you type into the address bar that isn't a url defaults to whatever search engine you have active next to it? I always keep Wikipedia active in the search bar and when I tried to Google something today with the address bar it did a Wikipedia search. What's the point of using the address bar to search if we have to change the search engine in the search box anyway?

more options

I have never looked at Google Chrome--haven't had a need to, so far.

I don't quite understand why a new user interface would mandate removal of options that users have indicated they feel strongly about. I'll assume that if this is the case, the developers have their reasons. Doesn't change my aversion to it, though.

more options

I think Firefox is going to lose a lot more users when Australis is fully set up. So many people have indicated that they dislike the idea of dumbing down the interface. I plan to switch to 24esr, and when that runs out, probably SeaMonkey. Others have already switched to PaleMoon, or some other Firefox clone, or to SeaMonkey. Too bad Camino is dead. That was the only Firefox clone for Mac OS.

more options


The Search Bar is going to be eliminated, in lieu of using the Location Bar for searches entirely, ala Chrome. A method of changing the Search engine to be used hasn't yet appeared in the UX Nightly builds, so the UX Nightly still has the Search Bar like the Releases do.

I am dismayed at all these changes being implemented so long before before Australis is released, because if Mozilla should decide not to "land" Australis all these preparatory changes in Firefox would be for naught. We would end up with so much "removed" and no "happy ending".


As far as Mozilla losing Firefox users to other Gecko browsers, do you have any data to back up that statement. Or you dealing with conjecture and threats posted here and at MozillaZine?

The statistics that I have been viewing show Firefox gaining users by actual numbers, and having fairly normal fluctuations in the per centage of use (visits) on a month to month basis. No sharp drops to reflect a mass migration to other browsers. And on weekends when users aren't at work (for the most part) and can use the browser of their choice, Firefox increases in usage have been stable for quite awhile.

more options

It's funny, but one of the main reasons I reverted to Firefox 22 rather than simply move to Safari was that Safari doesn't have the Search bar and uses the location bar for everything.

As for your statistics, well, Firefox is a great browser--of course it attracts users. By doing away with features some users prefer, though, it is creating a market for browsers that will meet our needs--and that's not a threat, it's a choice Mozilla has made with its eyes open.

more options

Wow. The reason I used Firefox was because it wasn't crap like Chrome. Now that its turning into Chrome 0.5 I guess I'll need to find a new browser. Thanks for turning Firefox into a crappy Chrome knock-off, Mozilla.

Được chỉnh sửa bởi Rabid vào

more options

Starting with Firefox 23 the keyword.URL pref is no longer supported and it is no longer possible to specify the search engine for the location bar that way.
The search engine that is used in the location bar is the search engine that is selected in the search Bar on the Navigation Toolbar.
You can disable automatic searching via the location bar by setting keyword.enabled to false and use a (one letter) keyword search to use a specific search engine instead to search via the location bar.

Another possibility is to disable keyword search (keyword.enable = false) and use a (one letter) keyword search for searching via the location bar.
You can set a keyword for an installed search engine via "Manage Search Engines" (click the search engines icon on the search bar).
That also allows to switch easily between search engines when searching via the location bar and you also do not have a problem with one word searches.

See also:

more options

I sympathise. My first reaction was annoyance at another feature removed from Firefox that I find valuable. But I thought it through and, given their reasons, it does make some sense (although I am still not fully convinced that I like it).

The reasoning behind this is (as I interpret): With many more websites becoming like apps with UIs like desktop software it is becoming more important that developers can customise the UI using Javascript. If a user disables some elements of Javascript it can break that UI. Personally, I know enough about the browser to figure out how I want to make it work but, Mozilla reasons, many users don't.

The key argument, I suppose, is that if we (Mozilla & community) are going to implement Javascript in the browser then the browser should do what the script tells it to do. If a website is abusing the power of Javascript, it is the website owner we need to get to change their bad habits - contact them and tell them you don't like it. If they don't stop, stop going to their website.

The other key argument is, there are already very good and well-established addons - e.g. NoScript - that can take care of the problem of abusive websites. Pointing the community in the direction of these good addons might educate them more on the issue of web security. Though I am not convinced something like NoScript is the easier option (if we are trying to make life easier for novices) it at least does things in a more upfront way then the options hidden away in Firefox's options dialog and could be a good learning experience for novices giving them an active part to play in securing their browser rather than a "set-and-forget" mentality encouraged by the removed options dialog.

Mozilla is attempting to streamline Firefox as many of the recent criticisms have been that it is too complex, bloated and slow. Many people are moving to Chrome because of this. They are making some progress in addressing these issues.

It seems to be a case of "you're damned if you do and you're damned if you don't". They can't please everybody.

But at least expert users still have these options via the about:config interface and I am happy enough to use that for now and and addon to reintroduce the options menu seems like the best solution to this issue all round.

Again, I am not 100% convinced, but I can see and understand the reasons for it.

Được chỉnh sửa bởi mt3ch vào

more options

@Waka_Flocka_Flame, re: http://limi.net/checkboxes-that-kill

That was a good article explaining the reasons why Mozilla has made these changes. It is a pity that he does not have comments turned on there.

As he talks about not providing features for the 2% of people they benefit at the risk of breaking the Web for the 98% of people they don't benefit, I wanted to ask him: Before they decided to remove these features, did they do any measurement of how many of those 98% actually did actually end up breaking the web via these features - for example, via counting support questions posted at support.mozilla.com?

As usability metrics and measurement seem to be important to Mozilla, they should be measuring the flip-side of their arguments and make sure they are not just making assumptions about them that could be as worthless as the assumptions that led them to implement these features in the first place. i.e. if nobody was actually affected negatively by the inclusion of these options, there really is no reason to remove them and inconvenience the 2% who do use them. (I'm thinking back to the removal of the "Email link" from the context menu which I used a lot).

Maybe someone here can answer that. Thanks.

Edit: Apologies, I know this isn't a discussion forum. I will find another venue to discuss this issue. But I will leave this post here as an answer to my question it may be helpful to the original questioner.

Được chỉnh sửa bởi mt3ch vào

more options

Maybe this addon can help get the checkboxes back.

more options


I have read a lot of newsgroup messages and forum messages from people saying that they have switched or are going to switch to Opera, SeaMonkey, PaleMoon, Safari, or Internet Explorer or some clone of it.

If the search bar is going to be eliminated as well as the keyword, which is already gone, does that not mean that search engines will have to be started from bookmarks, as in Firefox 2? What is the point of changing the search for the address bar to a search bar engine if the search bar is going to vanish? Is that not a lot of effort for nothing?

more options

I swear to god if Opera 15 gets bookmarks and a customizable UI I'm switching.

  1. 1
  2. 2