Recommended Posts

Yeah, it won't make 6, at the very earliest they're looking at 7 or 8 to get the first implementation.

And 64bit still isn't supported, since there's still bugs holding it up (One missing feature was just implemented a couple of days ago, but it's just a base for other features)

http://www.tomsguide.com/us/mozilla-firefox-developer-beta-aurora-browser,news-10961.html

I agree Mozilla need dedicated blog, which is not very technical and tell us about every update in Aurora and Nightly builds. Mozilla should also try to simplify all plans for users and Make FF 5 aurora to FF 4.5

Looking better by the days. That's why I still use 3.6 and skip ff4 like I did with vista :)

Firefox 4 is miles ahead of firefox 3.6. Why one earth would you skip it?

Is Mozilla working on Restart less addon stuff?

https://bugzilla.mozilla.org/show_bug.cgi?id=613294

Some addons already don't require a restart. I can't think of any specific examples right now though.

Firefox 4 is miles ahead of firefox 3.6. Why one earth would you skip it?

Beside the lame HA implementation compare to IE9's, FF4 TM+JM doesn't make FF4 feel any faster than FF3.6 even if it perform better in benchmark. Beside, some of the important addons I use still work better in 3.6 than it is in 4.0. I'll wait for 4.0.1, but I guess 5.0 is likely the next update as they have copied Chrome's numbering scheme.

Beside the lame HA implementation compare to IE9's, FF4 TM+JM doesn't make FF4 feel any faster than FF3.6 even if it perform better in benchmark. Beside, some of the important addons I use still work better in 3.6 than it is in 4.0. I'll wait for 4.0.1, but I guess 5.0 is likely the next update as they have copied Chrome's numbering scheme.

Firefox 4.0.1 is due very soon actually. IMHO there is no reason to skip 4.0, as it is a solid browser release and giving 3.6 a run for its money.

That's because your computers are kind of slow. Have you tried disabling HW acceleration?

I don't have slow computers, all of my computers can run Oblivion, but I digress,

Yes.

Additionally I tried IE9 with HW enabled and it is blazing fast.

Additionally I tried Chrome and it is blazing fast.

Additionally I tried Opera and it is blazing fast.

I don't have slow computers, all of my computers can run Oblivion, but I digress,

Yes.

Additionally I tried IE9 with HW enabled and it is blazing fast.

Additionally I tried Chrome and it is blazing fast.

Additionally I tried Opera and it is blazing fast.

Yep, lots-a-Gifs->"opens chromium" for me too but I rarely visit websites filled with gifs so no problems here. Anyway, any links where Fx crawls (one that isn't just filled with gifs for the purpose of filling it with gifs)?

Major advantages of FF3.6 over FF4.0 include better scrolling performance and better GIF performance.

That's absurd! Firefox 4 has much better smooth scrolling, especially on pages with fixed images as the background which were notoriously laggy on firefox 3. The inclusion of layers makes scrolling much more efficient and firefox 4 doesn't have to constantly redraw the page like firefox 3. Sounds like a bug on your machine if its slower. Scrolling has noticeably smoother on my machines, especially on my lowest end one (laptop, 2ghz core2duo, hd2600)

http://weblogs.mozillazine.org/roc/archives/2010/07/retained_layers.html

That's absurd! Firefox 4 has much better smooth scrolling, especially on pages with fixed images as the background which were notoriously laggy on firefox 3. The inclusion of layers makes scrolling much more efficient and firefox 4 doesn't have to constantly redraw the page like firefox 3. Sounds like a bug on your machine if its slower. Scrolling has noticeably smoother on my machines, especially on my lowest end one (laptop, 2ghz core2duo, hd2600)

http://weblogs.mozillazine.org/roc/archives/2010/07/retained_layers.html

On all *three* of my machines.

Also both of these are confirmed bugs.

Also the scrolling performance regression happened after retained layers.

Retained layers themselves increased performance.

I now use Yet Another Smooth Scrolling because it makes keyboard scrolling faster which visually decreases noticeable stuttering.

On all *three* of my machines.

Also both of these are confirmed bugs.

Also the scrolling performance regression happened after retained layers.

Retained layers themselves increased performance.

I now use Yet Another Smooth Scrolling because it makes keyboard scrolling faster which visually decreases noticeable stuttering.

I used to use YASS extension, but it was causing my scroll stuttering problem. Then I switched to:

http://smoothwheel.mozdev.org/

And it's 100% better in every way, for me at least. Solved all the problems I had with scroll stutter.

For these scrolling extensions, specifically the keyboard up/down scroll, is there a way to disable that slight delay that occurs before the page really starts scrolling? I don't like having to press and hold the up/down button for a second before the scrolling starts. I'd rather it happen as soon as I press it.

Stutter is not YASS related for me. I installed YASS to try to hide it.

Additionally, unlike Chrome, Firefox likes to keep the cursor interacting with the web page elements when scrolling. IE: Scroll over (cursor must be aligned so it would find itself over Services) Services and it will try to render the opened down Services menu, which laggs scrolling.

For these scrolling extensions, specifically the keyboard up/down scroll, is there a way to disable that slight delay that occurs before the page really starts scrolling? I don't like having to press and hold the up/down button for a second before the scrolling starts. I'd rather it happen as soon as I press it.

Just tried smoothwheel and that delay is not good, same delay on 6.0 and 5.0...

I like the way Chrome does it. Good step size, instant response, no acceleration, and no smoothing.

...For arrow key scrolling, mouse wheel scrolling is OK.

Stutter is not YASS related for me. I installed YASS to try to hide it.

Additionally, unlike Chrome, Firefox likes to keep the cursor interacting with the web page elements when scrolling. IE: Scroll over (cursor must be aligned so it would find itself over Services) Services and it will try to render the opened down Services menu, which laggs scrolling.

Just tried smoothwheel and that delay is not good, same delay on 6.0 and 5.0...

I like the way Chrome does it. Good step size, instant response, no acceleration, and no smoothing.

...For arrow key scrolling, mouse wheel scrolling is OK.

That's strange then, I don't have any sort of delay when I start scrolling.

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

    • No registered users viewing this page.
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop data 'Google Chrome' is downloading for Chrome without you agreeing to it. Fun right? Sure, the way Microsoft is pushing 'Microsoft Edge' on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!