Recommended Posts

hey I had some other lines also that I'd like to ask if they are now obsolete or not

user_pref("browser.turbo.enabled", true);

Completely obsolete, does nothing.

"Pref removed (obsolete). Previously:

Determined whether to load browser in "Turbo Mode" (aka "quick launch") (Windows/Mozilla Suite only)

True: Load some Mozilla code into memory on Windows boot

False (default): Load browser normally on program execution"

user_pref("network.dns.disableIPv6", true); <--- increases speed when disabled?

Up to you, I've found it does increase page loading times a little, but it kind of messed up large file download speeds for me on some sites.

user_pref("network.enableIDN", false);

"Determines whether to use IDN (International Domain Name) support in the browser"

No reason to turn it off really. Was a security issue for about a week til they fixed it.

user_pref("browser.tabs.showSingleWindowModePrefs", true);

"Determines whether to display "Single Window Mode" settings in preferences.

True: Show "Force links that open in new windows to open in..." options under "Tools → Options → Advanced → Tabbed Browsing"

False (default): Opposite of above"

Pretty sure they're shown by default now in 1.5

user_pref("content.switch.threshold", 750000); <--- I have it at 750,000 instead of 200,000. What does that line do?

"Determines how long to wait for user input (mouse movement or typing) in microseconds until switching to low frequency interrupt mode. (High frequency interrupt mode provides better UI responsiveness at the expense of load time.) Default value is 750000."

user_pref("extensions.dss.enabled", 1); <--- This doesnt work at all. I dont remember where I got the info to put that line (which is dynamic skin switch)

"True: Enable dynamic skin (theme) switching.

False (default): Require a browser restart when switching themes.

Note: Switching themes dynamically is buggy"

user_pref("browser.sessionhistory.max_total_viewers", 5); <-- to load from cache?

"Determines the maximum number of content viewers to cache for "bfcache" (fast back/forward navigation). Default value is -1 (calculate based on available memory). All values less than 0 are equivalent.

Note: Firefox 1.5 and above only."

Info from here :

http://kb.mozillazine.org/Firefox_:_FAQs_:...:config_Entries

hey I had some other lines also that I'd like to ask if they are now obsolete or not

user_pref("browser.turbo.enabled", true);

user_pref("network.dns.disableIPv6", true); <--- increases speed when disabled?

user_pref("network.enableIDN", false);

user_pref("browser.tabs.showSingleWindowModePrefs", true);

user_pref("content.switch.threshold", 750000); <--- I have it at 750,000 instead of 200,000. What does that line do?

user_pref("extensions.dss.enabled", 1); <--- This doesnt work at all. I dont remember where I got the info to put that line (which is dynamic skin switch)

user_pref("browser.sessionhistory.max_total_viewers", 5); <-- to load from cache?

Explains each about:config setting

The Turbo one was for faster launching Firefox nothing to do with browsing, and it's obsolete.

The IPv6 setting Determines whether to perform IPv6 name lookups, so if it's disabled I'm sure it will give a slight performance improvement.

user_pref("network.enableIDN", false); Determines whether to use IDN (International Domain Name) support in the browser. So again you might see a slight improvement. And I think this was used as a security fix work around at one time. Meaning it plug a security hole...but that's since been fixed.

user_pref("browser.tabs.showSingleWindowModePrefs", true);Determines whether to display "Single Window Mode" settings in preferences. Nothing to do with speed at all.

user_pref("content.switch.threshold", 750000);Determines how long to wait for user input (mouse movement or typing) in microseconds until switching to low frequency interrupt mode. (High frequency interrupt mode provides better UI responsiveness at the expense of load time.) Default value is 750000. So the highter the threshold the better performance, I guess? This one is a little over my head.. but that's what it looks like.

user_pref("extensions.dss.enabled", 1); You are correct about that one, it's a dynamic skin switch, and they say it's buggy.. on that page.

user_pref("browser.sessionhistory.max_total_viewers", 5);Determines the maximum number of content viewers to cache for "bfcache" (fast back/forward navigation). Default value is -1 (calculate based on available memory). All values less than 0 are equivalent.

Note: Firefox 1.5 and above only. Supersedes browser.sessionhistory.max_viewers. This has to do with the fast back/forward feature as mentioned above..and btw has been said to cause high memory usage. This is what the developer was trying to explain and everyone jumped on the saying.. "high memory usage in Firefox is a feature" big joke to some anti-Firefox folks.

Most of these will give you very little speed boost, if any. IMHO

  • 2 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • About bloody time. I have got PRs with hundred of files and the Web UI just struggling to even load the pages.
    • I wonder if it was applying secure boot certificates/dbx files?
    • I recently tried edge. It seems a lot better. A lot of the junk in it is gone. It seems less bloated and snappy.
    • Lethal fake phone chargers are still being sold on Amazon and eBay, UK watchdog warns by Paul Hill Credit: Pexels The UK consumer rights organization, Which?, is claiming that “potentially lethal knock-off chargers” are still being sold on online marketplaces seven years after it exposed the danger of these chargers. In its latest investigation, it bought 15 USB phone chargers from several online marketplaces and found they were missing key information, meaning they cannot be legally sold in the UK. Which? bought the 15 chargers from seven online marketplaces. These were Amazon (including Amazon Haul), AliExpress, B&Q Marketplace, Debenhams Marketplace, and eBay. It said that the chargers were so badly made that anyone using them was at risk of electric shock. Over half the chargers also posed fire and explosion risks. Of the chargers purchased, one was a fake Apple USB-C 35W power adaptor charger. To confuse buyers, the box was branded with an Apple logo, but testing found it to be a fake. Further testing picked up arcing sounds after 10 seconds of use, where a current jumps between two parts of the electrical circuit, which can cause fires, explosions, or electric shock. The manufacturers of this particular charger also put modeling clay inside it to make it feel more weighty, robust, and genuine. Not all of the chargers were technically faulty; however, some were missing key packaging, markings, and documentation, meaning they can’t be sold in the UK legally. Which? said that it is now campaigning alongside a coalition of safety groups and businesses for new laws that make online marketplaces responsible for ensuring the safety of products that they choose to list on their websites. It also said the government needs to start using powers under the Product Regulation and Metrology Act, which was adopted last July, to impose safety requirements on online marketplaces via secondary legislation, but so far, there have been delays. No matter what country you are in, be sure to properly research what you are buying and only buy authentic chargers to prevent fires. You can read more about Which?’s research here.
    • Visual Studio finally gets long-awaited feature that developers will love by Usama Jawad Visual Studio Code is Microsoft's popular, lightweight, open-source code editor, it is actually Visual Studio that is the company's flagship integrated development environment (IDE). Although the IDE already offers a boatload of useful features for developers, Microsoft has finally introduced a long-requested capability that will be loved by many. While developers have already been able to create Git pull requests (PRs) directly within Visual Studio for the past couple of years, it had not been possible to review a PR without switching to the browser, until now. Microsoft revealed in December 2025 that it is working on UX that enables developers to do just that, and fast-forward to June 2026, and Visual Studio finally has native capabilities to open and inspect a PR, discuss feedback, and wrap up the review, all without switching to the browser. This integration works for both GitHub and Azure DevOps (including on-prem). Developers have access to multiple surfaces to open a PR, including Git Repository, Git Changes, and the Git menu in Visual Studio. Once you open a PR, all the important details will be immediately visible to you, from where you can navigate to various levels of granularity and branch states, depending on the reviews that you are engaged in. As you would expect, you also get a diff view that enables you to see code changes inline or side-by-side in a separate panel. You can also review commit-by-commit. Additionally, this UX fosters collaboration as you can leave comments, reply to threads, and resolve conversations easily. Naturally, you can also leverage Copilot to apply a code suggestion to fix a potential issue. When you are done, you have the ability to approve, complete, and merge the PR. This is a pretty major feature as it has been requested heavily for the past few years. You can try it out in Visual Studio 2026 version 18.7, made available here recently. Microsoft plans to enhance this experience further in future releases with comment filtering, a timeline of PR activity, and more.
  • Recent Achievements

    • Week One Done
      Timaximus earned a badge
      Week One Done
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Rookie
      FBSPL went up a rank
      Rookie
    • First Post
      davidbazooked earned a badge
      First Post
    • Week One Done
      davidbazooked earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      499
    2. 2
      PsYcHoKiLLa
      174
    3. 3
      +Edouard
      160
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!