Recommended Posts

You didn't look close enough because I'm not the only one who has this since I just used a script I found......

http://yaku.dk/s/scr...firefox4ftw.png

And you didn't read what he wrote.

Yes - by enabling the menu bar. AFAIK there's no official way to have the Firefox button and the menu off at once though.

The latest nightly seems to break tabs in titlebar implementations... or at least for me, the tabs get pushed down again :(

Same here. Using Minimal 1.0 skin, the tabs moved down a bit and the new tab button is messed up. But that's what you expect when you use nightly.

The latest nightly seems to break tabs in titlebar implementations... or at least for me, the tabs get pushed down again :(

for some reason i have a feeling it has to do with the new code added to make the menu button work in xp and the basic theme, should hopefully be fixed soon

SunSpider results (perfomed on laptop with win7 x64, core 2 duo 2ghz T5800, 3gb ddr2, nvidia 9200LE gpu):

I get a 2.4% speed improvement with SunSpider with ff4b3 compared to ff4b2 as you can see below:

Firefox 4.0 Beta 3:

RESULTS (means and 95% confidence intervals)
--------------------------------------------
Total:                  810.0ms +/- 2.4%
--------------------------------------------

  3d:                   132.8ms +/- 14.0%
    cube:                40.6ms +/- 17.9%
    morph:               39.0ms +/- 45.9%
    raytrace:            53.2ms +/- 10.6%

  access:               112.6ms +/- 5.0%
    binary-trees:        25.2ms +/- 15.4%
    fannkuch:            54.8ms +/- 3.0%
    nbody:               15.2ms +/- 53.8%
    nsieve:              17.4ms +/- 35.2%

  bitops:                34.8ms +/- 14.4%
    3bit-bits-in-byte:    1.2ms +/- 46.3%
    bits-in-byte:        15.2ms +/- 38.1%
    bitwise-and:          3.6ms +/- 52.4%
    nsieve-bits:         14.8ms +/- 11.0%

  controlflow:            9.4ms +/- 27.4%
    recursive:            9.4ms +/- 27.4%

  crypto:                52.8ms +/- 22.4%
    aes:                 27.4ms +/- 5.2%
    md5:                 16.8ms +/- 46.6%
    sha1:                 8.6ms +/- 50.7%

  date:                 106.6ms +/- 9.2%
    format-tofte:        65.0ms +/- 14.8%
    format-xparb:        41.6ms +/- 14.7%

  math:                  71.8ms +/- 15.2%
    cordic:              41.2ms +/- 19.7%
    partial-sums:        21.6ms +/- 26.3%
    spectral-norm:        9.0ms +/- 69.8%

  regexp:                67.6ms +/- 8.8%
    dna:                 67.6ms +/- 8.8%

  string:               221.6ms +/- 11.6%
    base64:              10.8ms +/- 57.2%
    fasta:               33.0ms +/- 26.8%
    tagcloud:            84.2ms +/- 5.7%
    unpack-code:         68.6ms +/- 6.6%
    validate-input:      25.0ms +/- 43.2%

Firefox 4.0 Beta 2:

RESULTS (means and 95% confidence intervals)
--------------------------------------------
Total:                  829.6ms +/- 3.4%
--------------------------------------------

  3d:                   132.2ms +/- 10.6%
    cube:                40.6ms +/- 17.8%
    morph:               40.8ms +/- 36.3%
    raytrace:            50.8ms +/- 19.5%

  access:               113.8ms +/- 14.2%
    binary-trees:        22.2ms +/- 2.5%
    fannkuch:            52.2ms +/- 2.6%
    nbody:               27.6ms +/- 56.6%
    nsieve:              11.8ms +/- 4.7%

  bitops:                34.6ms +/- 11.0%
    3bit-bits-in-byte:    1.0ms +/- 0.0%
    bits-in-byte:        10.6ms +/- 15.7%
    bitwise-and:          2.6ms +/- 64.2%
    nsieve-bits:         20.4ms +/- 3.3%

  controlflow:           11.0ms +/- 33.0%
    recursive:           11.0ms +/- 33.0%

  crypto:                53.0ms +/- 16.7%
    aes:                 29.0ms +/- 10.1%
    md5:                 14.8ms +/- 58.3%
    sha1:                 9.2ms +/- 58.4%

  date:                 107.0ms +/- 4.1%
    format-tofte:        66.0ms +/- 3.3%
    format-xparb:        41.0ms +/- 12.5%

  math:                  67.2ms +/- 8.5%
    cordic:              38.6ms +/- 9.3%
    partial-sums:        19.0ms +/- 0.0%
    spectral-norm:        9.6ms +/- 54.6%

  regexp:                75.0ms +/- 15.0%
    dna:                 75.0ms +/- 15.0%

  string:               235.8ms +/- 3.3%
    base64:               9.0ms +/- 0.0%
    fasta:               28.0ms +/- 4.4%
    tagcloud:            81.4ms +/- 3.2%
    unpack-code:         85.4ms +/- 11.1%
    validate-input:      32.0ms +/- 7.8%

Firefox 3.6.8:

RESULTS (means and 95% confidence intervals)
--------------------------------------------
Total:                 1268.8ms +/- 4.0%
--------------------------------------------

  3d:                   219.6ms +/- 24.1%
    cube:                57.2ms +/- 13.2%
    morph:               65.8ms +/- 14.2%
    raytrace:            96.6ms +/- 45.4%

  access:               190.2ms +/- 5.0%
    binary-trees:        50.2ms +/- 15.5%
    fannkuch:            82.2ms +/- 7.4%
    nbody:               33.2ms +/- 20.4%
    nsieve:              24.6ms +/- 29.2%

  bitops:                60.4ms +/- 17.6%
    3bit-bits-in-byte:    4.0ms +/- 38.1%
    bits-in-byte:        16.0ms +/- 22.7%
    bitwise-and:          4.8ms +/- 53.1%
    nsieve-bits:         35.6ms +/- 39.6%

  controlflow:           53.8ms +/- 24.5%
    recursive:           53.8ms +/- 24.5%

  crypto:                69.0ms +/- 19.7%
    aes:                 36.6ms +/- 20.2%
    md5:                 18.4ms +/- 17.0%
    sha1:                14.0ms +/- 55.8%

  date:                 200.2ms +/- 10.9%
    format-tofte:        99.4ms +/- 9.0%
    format-xparb:       100.8ms +/- 15.3%

  math:                  80.0ms +/- 17.0%
    cordic:              37.4ms +/- 13.2%
    partial-sums:        28.4ms +/- 50.8%
    spectral-norm:       14.2ms +/- 42.6%

  regexp:                68.6ms +/- 12.9%
    dna:                 68.6ms +/- 12.9%

  string:               327.0ms +/- 6.5%
    base64:              18.4ms +/- 36.9%
    fasta:               74.0ms +/- 8.1%
    tagcloud:            90.8ms +/- 6.5%
    unpack-code:        104.2ms +/- 13.4%
    validate-input:      39.6ms +/- 18.8%

With 1 tab open firefox 4b3 uses 59mb ish ram, firefox 4b2 used 82mb ish ram, firefox 3.6.8 uses 60mb ish.

Nags with the beta.

Apparently you can no longer get rid of the annoying tab scroll (who the F wants to scroll through a whole bunch of tabs... they need new UI/usablity designers)

also Who thought it was a good idea to remove the min,max,close widgets.... seriously, that's more annoying than apps that use non standard size/position widgets. again, they need new UI/Usability designers.

When you think FF can't get more stupid, the designers go an prove you wrong again.

Nags with the beta.

Apparently you can no longer get rid of the annoying tab scroll (who the F wants to scroll through a whole bunch of tabs... they need new UI/usablity designers)

also Who thought it was a good idea to remove the min,max,close widgets.... seriously, that's more annoying than apps that use non standard size/position widgets. again, they need new UI/Usability designers.

When you think FF can't get more stupid, the designers go an prove you wrong again.

Hm? Do you mean the min/max/close widgets provided by Windows? They should still be there. :blink:

Firefox 4.0 Beta still has a problem that has changed a bit but not much.

Beta 1 if I launched it from restore with eg 6 tabs it would lag and then half of the time it would crash and I don't have a slow computer.

Beta 2 it would launch but take quite a while and almost crash.

Beta 3 A tiny bit faster again but still around 10-20 seconds.

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

    • No registered users viewing this page.
  • Posts

    • I have been using Firefox for years.
    • I'd trust open source stuff on github more then closed source binaries from Microsoft.
    • OpenAI is now rolling out Lockdown Mode to more ChatGPT users by Pradeep Viswanathan Back in February, OpenAI first announced Lockdown Mode for users who want the most comprehensive protection from potential attacks. At the time of the announcement, the company mentioned that this feature was available to a small set of highly security-conscious users, including executives or security teams at leading organizations. Today, OpenAI announced that Lockdown Mode is now rolling out to all personal ChatGPT accounts, including Free, Go, Plus, and Pro, and also self-serve ChatGPT Business accounts. Users can enable the feature from ChatGPT Settings > Security when it is available for their account. When Lockdown Mode is enabled, ChatGPT limits or disables several features that connect to the web or external services. These include live web browsing, Deep Research, Agent Mode, and more. Here is the complete list of services that will be disabled in Lockdown Mode: Live web browsing: Web browsing is limited to accessing only cached content. Search results may be limited, unavailable, or stale. Image support: ChatGPT may not display images in regular responses or retrieve images from the web. Users can still upload image files, and image generation remains available where it is otherwise available. Deep research: Deep research is disabled. Agent mode: Agent mode is disabled. Canvas networking: Users cannot approve Canvas-generated code to access the network. File downloads: ChatGPT cannot download files for data analysis. ChatGPT can still operate on your manually uploaded files. It is important to note that Lockdown Mode does not completely block prompt injections from appearing in content that ChatGPT processes. For example, a malicious instruction could still be present in an uploaded file or cached web content. However, the mode is designed to reduce the ways such an attack could send sensitive information outside the conversation. Along with Lockdown Mode, OpenAI today also announced that the Active sessions feature is now available across ChatGPT accounts and workspace types. This feature allows users to review where their account is signed in across devices and end sessions if required. A session will have the following information displayed: Device or browser information. First-party app context, such as ChatGPT, Codex, or API Platform. Approximate location. Sign-in date and time. Whether the device is a trusted device. Whether it is your current session. OpenAI highlighted that the Active sessions feature will not be available for accounts linked to an organization’s single sign-on setup, including SAML or OIDC.
  • Recent Achievements

    • Rookie
      moog19 went up a rank
      Rookie
    • Mentor
      grik went up a rank
      Mentor
    • Dedicated
      JKR earned a badge
      Dedicated
    • One Year In
      CHUNWEI earned a badge
      One Year In
    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
  • Popular Contributors

    1. 1
      +primortal
      491
    2. 2
      PsYcHoKiLLa
      270
    3. 3
      Skyfrog
      75
    4. 4
      Steven P.
      68
    5. 5
      FloatingFatMan
      63
  • Tell a friend

    Love Neowin? Tell a friend!