updates Meet the browser: Firefox Next

[grayscale]

At first I thought https will be trimmed as well. Since it only trims http websites, then I see no need on disabling it (I just updated now, I disabled auto update :D)

[bogas04]

Is it possible to disable the "Hide http" feature?

There's an about:config entry to disable it. I read it from mozillazine. I will post it if I find it again.

To disable "hiding of http" feature , use this about config value and toggle it to false

browser.urlbar.trimURLs

There is a new landing in the UX branch

Expect TI in mc by 1st week of july

Firefox 6 to beta and Firefox 7 to aurora branch would happen on 5th July

I have updated the first page with many links to track the development , also , now that firefox has opted for faster release cycle , i dont think we would be creating more of these threads every quarter! Just like opera and chrome threads are there , i think firefox should follow the same. So henceforth all firefox discussion about PRERELEASE versions would go here, as it was decided at advent of the release mechanism

[+Zlip792 MVC]

Azure (Implement Direct2D Azure Backend) landed in mozilla-inbound

https://bugzilla.mozilla.org/show_bug.cgi?id=651858#c101

Soon in mozilla-central.........Yuppeee!!!!!!!

[+Heartripper Subscriber¹]

Azure (Implement Direct2D Azure Backend) landed in mozilla-inbound

https://bugzilla.mozilla.org/show_bug.cgi?id=651858#c101

Soon in mozilla-central.........Yuppeee!!!!!!!

very good! (Y)

[+Heartripper Subscriber¹]

i'm really amazed with nightly memory usage; once when i randomly opened the task manager to check the usage, it usually showed about 250 - 300 mb usage; but now it's usually around 140 - 170 mb, great work mozilla! :laugh:

[Guest mattburles]

are we going to see any UI changes in firefox 6? i know there wasnt any from 4 to 5.

[Aaron Olive]

Latest results

[remixedcat]

are we going to see any UI changes in firefox 6? i know there wasnt any from 4 to 5.

I hope not I like it the way it is.

[The_Decryptor Veteran]

So Azure has landed, and is enabled by default. On some things it gives massive gains, while on other things it barely helps. But more performance is always welcome.

Edit: Well, D2D backed <canvas>, there's still work to be done for general page compositing and cross-process stuff.

[+Gary7 Subscriber²]

Starting with Today's Nightly build , when I hover over the icon in the taskbar, I can't see a preview. All I see is a busy Aero mouse pointer. Anyone else see this? Using Win 7 x 64

[Brandon H Supervisor]

Starting with Today's Nightly build , when I hover over the icon in the taskbar, I can't see a preview. All I see is a busy Aero mouse pointer. Anyone else see this? Using Win 7 x 64

working fine here, also Win 7 x64

[Karl-Johan]

Starting with Today's Nightly build , when I hover over the icon in the taskbar, I can't see a preview. All I see is a busy Aero mouse pointer. Anyone else see this? Using Win 7 x 64

Same here.

[+Gary7 Subscriber²]

working fine here, also Win 7 x64

Switch on the setting of "Show tab preview in windows taskbar"(in tab options) and then look.

[Karl-Johan]

Switch on the setting of "Show tab preview in windows taskbar"(in tab options) and then look.

Edit: There's more people experiencing the same problem over here. http://forums.mozillazine.org/viewtopic.php?f=23&t=2236367&start=30

[+Gary7 Subscriber²]

Edit: There's more people experiencing the same problem over here. http://forums.mozillazine.org/viewtopic.php?f=23&t=2236367&start=30

That was for Brando212, as he said he does not see the busy aero mouse pointer and you won't if that is NOT checked.

[Brandon H Supervisor]

That was for Brando212, as he said he does not see the busy aero mouse pointer and you won't if that is NOT checked.

ah i see now, i forgot they turned that into a optional setting

[Udedenkz]

I hope electrolysis project will help Firefox in performance.

I am not super-optimistic though.

Currently there are a few major issues:

1. Firefox tab animations are very laggy compared to Chrome.

Loading new tab pages in a separate process (or at least separating the FF GUI process...) will help here.

Although, part of the issue seems just to stem from expensive repainting in general (new tab animation laggs opening a blank).

From visual analysis, Chrome tabs seem more simple.

2. Firefox expensively loads background tabs.

Firefox repaints the content in background tabs (correct me if I am wrong).

This is painfully seen loading a 2-3MB image in a background tab (while foreground tab is idle),

simply downloading something is not CPU intensive but Firefox uses 30% to load an img in background tab.

3. All loading tabs and foreground tab are required to share on virtual core.

The main component! The slower each virtual core is, the worse Firefox performance is.

This will not benefit single core systems, but will HT and better CPUs.

I have been using Firefox 7a for some time now, but it is painful because of the above.

Azure and TI are not as important. They are simple improvements to something that "works well", whereas process separation is an improvement to something that "works poorly"...

Edited June 27, 2011 by Udedenkz

[max22]

i'm really amazed with nightly memory usage; once when i randomly opened the task manager to check the usage, it usually showed about 250 - 300 mb usage; but now it's usually around 140 - 170 mb, great work mozilla! :laugh:

Same here! So far ok but not yet convinced. Need to give it a good week before I am happy maybe two.

I hope electrolysis project will help Firefox in performance.

I am not super-optimistic though.

Currently there are a few major issues:

1. Firefox tab animations are very laggy compared to Chrome.

Loading new tab pages in a separate process (or at least separating the FF GUI process...) will help here.

Although, part of the issue seems just to stem from expensive repainting in general (new tab animation laggs opening a blank).

From visual analysis, Chrome tabs seem more simple.

2. Firefox expensively loads background tabs.

Firefox repaints the content in background tabs (correct me if I am wrong).

This is painfully seen loading a 2-3MB image in a background tab (while foreground tab is idle),

simply downloading something is not CPU intensive but Firefox uses 30% to load an img in background tab.

3. All loading tabs and foreground tab are required to share on virtual core.

The main component! The slower each virtual core is, the worse Firefox performance is.

This will not benefit single core systems, but will HT and better CPUs.

I have been using Firefox 7a for some time now, but it is painful because of the above.

Azure and TI are not as important. They are simple improvements to something that "works well", whereas process separation is an improvement to something that "works poorly"...

I highly disagree.

Though the improvements are fine by me but I am in no rush. Runs smooth as butter for me.

[bogas04]

I hope electrolysis project will help Firefox in performance.

I am not super-optimistic though.

Currently there are a few major issues:

1. Firefox tab animations are very laggy compared to Chrome.

Loading new tab pages in a separate process (or at least separating the FF GUI process...) will help here.

Although, part of the issue seems just to stem from expensive repainting in general (new tab animation laggs opening a blank).

From visual analysis, Chrome tabs seem more simple.

2. Firefox expensively loads background tabs.

Firefox repaints the content in background tabs (correct me if I am wrong).

This is painfully seen loading a 2-3MB image in a background tab (while foreground tab is idle),

simply downloading something is not CPU intensive but Firefox uses 30% to load an img in background tab.

3. All loading tabs and foreground tab are required to share on virtual core.

The main component! The slower each virtual core is, the worse Firefox performance is.

This will not benefit single core systems, but will HT and better CPUs.

I have been using Firefox 7a for some time now, but it is painful because of the above.

Azure and TI are not as important. They are simple improvements to something that "works well", whereas process separation is an improvement to something that "works poorly"...

True , or just taking chrome out as a separate process would do enough to keep the UI fast

[BoneyardBrew Member]

I'd definitely agree that the UI is sluggish. Hell, even running your cursor up and down the Firefox menu isn't as responsive as it should be.

Boot times are still pretty trashy for me, even on an SSD. :/

[Gaffney]

The UI on firefox 7.0a is fine for me but firefox still crashes sort of often for me. Maybe once a day, chrome just seems to glide. I use both of them anyway but mostly chrome. The tests are catching up with Chrome.

[bogas04]

The UI on firefox 7.0a is fine for me but firefox still crashes sort of often for me. Maybe once a day, chrome just seems to glide. I use both of them anyway but mostly chrome. The tests are catching up with Chrome.

Palemoon hmm, they should make nightly builds too :p

[ViperAFK]

I'd definitely agree that the UI is sluggish. Hell, even running your cursor up and down the Firefox menu isn't as responsive as it should be.

Boot times are still pretty trashy for me, even on an SSD. :/

Opens instantly on my ssd. I do agree the UI is sluggish compared to other browsers though.

[max22]

I'd definitely agree that the UI is sluggish. Hell, even running your cursor up and down the Firefox menu isn't as responsive as it should be.

Boot times are still pretty trashy for me, even on an SSD. :/

What are your boot times ?

The UI on firefox 7.0a is fine for me but firefox still crashes sort of often for me. Maybe once a day, chrome just seems to glide. I use both of them anyway but mostly chrome. The tests are catching up with Chrome.

I never had Firefox 7.0a crash on me ever. It has had the occasional annoying bug or problem but no crashes. That is to be expected with a alpha build of a program though. It glides for me just like my friend's Chrome on his pc. Actually Firefox feels faster than Chrome now.

[dnast]

Never had 7.0a crash on me, either. In fact, I just checked and I've only had 7 crashes this year and I've been using Nightly/Minefield as my main browser the whole time (except for a week of trying Aurora).

I don't understand how it crashes so much on other people's systems.