Meet Firefox 4.0.1

[mNiosu]

The render-mode preference is outdated, Direct2D is controlled by it's own pref now.

And the DirectWrite pref is only there so you can mix it with old GDI rendering, mainly for performance testing I would think (Since it'd be slower than plain GDI or plain Direct2D)

So in conclusion I should use value 0 for pure Direct2D ? You got me confused... :)

[+Audioboxer Subscriber²]

Beta 6 release date?

[Hawk999]

Beta 6 release date?

Google is your friend:

https://wiki.mozilla.org/Releases

[Drifus]

I made some customizations to Firefox 4 b5 aiming for a clean and minimalist look. Tested on Windows 7 with custom theme.

/* Font Tweaks*/
menubar, menubutton, menulist, menu, menuitem, textbox, toolbar, tab, .tab-text, tree, tooltip {
    font-size: 8pt !important;
    font-family: Calibri !important;
}

/* Remove the URL bar Go button*/
#go-button {
    display: none !important;
}

/* hide the Search Engine image*/
.searchbar-engine-image {
    display: none !important;
}

/* remove the search button (magnifying glass)*/
.search-go-button {
    display: none !important;
}

/* Kill bookmark icons in the Personal Toolbar*/
toolbarbutton.bookmark-item > .toolbarbutton-icon {
    display: none !important;
}

/*Hide Firefox Sync Statusbar Icon*/
#sync-status-button {
    display: none !important;
}

/*Disable tabstoolbar drag - enable newtab double clicking*/
#TabsToolbar {
    -moz-binding: none !important;
}

/*Transparent Firefox Button - no text*/
#appmenu-button {
    padding: 5px 28px 3px 0px !important;
    margin-top:3px !important;
    background-color: transparent !important;
}
#appmenu-button .button-text {
    display: none !important;
}

/*Reduce titlebar margin - choose margin according your windows theme (minimize, maximize close buttons)*/
#main-window {
    margin-top: -7px !important;
}
#main-window[sizemode="maximized"] {
    margin-top: -4px !important;
}

/*Remove some dropmarkers*/
#back-forward-dropmarker {
    display: none !important;
}
#urlbar > .autocomplete-history-dropmarker {
    display: none !important;
}
/*Transparency, hover and more naked UI*/
#PersonalToolbar, #nav-bar {
    background-color: transparent !important;
    border: none !important;
}
#nav-bar {
    margin-top: 1px !important;
}
#urlbar, #searchbar > *, #search-box {
    -moz-appearance: none !important;
    background: transparent !important;
    color: #000000 !important;
    border: none !important;
    -moz-box-shadow: none !important;
    height: 22px !important; /*Fix searchbar height without magnifying glass and search engine icon*/
}
#urlbar:hover, #searchbar:hover > *, .findbar-textbox:hover {
    background: rgba(255,255,255,.5) !important;
}
#browser-bottombox, #status-bar, #status-bar > *, #ybToolbar {
    background: rgba(255,255,255,.07) !important;
    -moz-appearance: none !important;
    border: #000000 !important;
}
.tabbrowser-tab:not([selected="true"]) {
    background: rgba(0,0,0,0.2) !important;
    color: #eeeeee !important;
    text-shadow: none !important;
}
.tabbrowser-tab[selected="true"] {
    background-image: -moz-linear-gradient(left, transparent, transparent 1px, rgba(255,255,255,.5) 1px, rgba(255,255,255,.5)) !important;
}
.tabs-newtab-button {
    background: transparent !important;
    border: #000000 !important;
}
.tabs-newtab-button:hover, #new-tab-button:hover, .scrollbutton-down:hover, .scrollbutton-up:hover, #alltabs-button:hover, #tabview-button:hover {
    -moz-appearance: none !important;
    background: none !important;
    border: #000000 !important;
}
.toolbarbutton-1 > .toolbarbutton-menubutton-button, .toolbarbutton-1 > .toolbarbutton-menubutton-dropmarker, .toolbarbutton-1 {
    background: transparent !important;
    border: none !important;
    -moz-box-shadow: none !important;
}

[The_Decryptor Veteran]

So in conclusion I should use value 0 for pure Direct2D ? You got me confused... :)

Just leave it on the default setting (which is -1, just right click on it and select reset)

[mNiosu]

Just leave it on the default setting (which is -1, just right click on it and select reset)

Ok, thanks for clearing.

By the way noticed that i forgot to edit the "max version" in the fission add-on so you don't need to disable compatibility reporter so here it is: BETA 5 -> LINK ; BETA 6 - > LINK!!

[Knaarfje]

The beta is incredibly sluggish for me, even with every addon disabled.. switching a tab takes like a second. Is this a known problem?

[Udedenkz]

The beta is incredibly sluggish for me, even with every addon disabled.. switching a tab takes like a second. Is this a known problem?

The ones I know are,

- Rendering Glitches w. Flash and D2D/D3D

- Severe Performance issues w. Flash and D2D in some cases

- Animated GIFs rape the CPU as of a week or so ago

- Scrolling was much smother ~10 days ago

- DownloadThemAll! uses more CPU w. D2D enabled

All these are known btw.

[aznkid25]

Looks like the first build of Firefox 4 Beta 6 might be coming out later today.

Source

ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b6-candidates/build1/

Also, found this article:

Firefox 4 Beta 6 renamed to Beta 7; new, small Beta 6 inserted

[The_Decryptor Veteran]

Uh, hardware acceleration is on by default in Firefox, the bug they're talking about on Windows is in the networking code.

[Inklin]

B7pre out todayhopefully coming changes for b7 will bring the more refined look that we saw in their mock-up... especially with the url bar.

[+Frank B. Subscriber²]

The version bump to 4.0b7pre took place today.

For what it's worth, I had to manually download today's nightly - the automatic update was stuck on 'Checking for updates...' (using yesterday's 4.0b6pre OS X build if it matters).

You can download today's nightly manually from here.

[aznkid25]

Firefox 4 beta 6 build 1 now available:

ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b6-candidates/build1/win32/en-US/Firefox%20Setup%204.0%20Beta%206.exe

Looks like build 2 is probably coming out very soon too.

[mNiosu]

Firefox 4 beta 6 build 1 now available:

ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b6-candidates/build1/win32/en-US/Firefox%20Setup%204.0%20Beta%206.exe

Looks like build 2 is probably coming out very soon too.

Strange. Combined stop-go-reload button not present in this release ...

[aznkid25]

Strange. Combined stop-go-reload button not present in this release ...

I noticed that too, even with a clean install. Build 2 is being released very soon. Hoping that it's a bug that will be fixed in that build. I'm not sure what happened.

[Darrian]

A lot of stuff from even last week's 4.0b6pre builds is not here. If they don't incorporate those features I'll probably end up going back to tinderbox builds until beta 7.

[+Gary7 Subscriber²]

A lot of stuff from even last week's 4.0b6pre builds is not here. If they don't incorporate those features I'll probably end up going back to tinderbox builds until beta 7.

Just continue with the Nightly builds. That is waht I am going to do.

[torrentthief]

beta 6 mearly fixes the most serious bugs in b5 it appears, don't expect anything other than the 2 bugs they stated would be fixed.

[Growled Member]

I was just wondering, why is Mozilla releasing so many betas of this? Other browsers would have already done been released.

[torrentthief]

other browsers have $100m's and 100's or 1000's of full-time programmers and testers, mozilla doesn't have those resources.

[Darrian]

Well, obviously the development up to the anticipated 4.0 is going to be relatively slow and I don't think it's even slated to be released until next year. This way people who don't even know about minefield builds can still see the progress being made in regular intervals.

[aznkid25]

But isn't beta 6 a feature freeze? Would beta 7 be released sooner then, if beta 6 is only fixing a few bugs?

[The_Decryptor Veteran]

I was just wondering, why is Mozilla releasing so many betas of this? Other browsers would have already done been released.

Mozilla's development schedule is set out so that features land over a series of betas, with one being the "feature complete" milestone (For 4.0, it was Beta 5, but they moved it to Beta 6 to allow for some more development time on some things, but now that they're releasing a beta fix for a crash they're fiddled with the names), then small fixes make it in up until the RC stage.

Other groups may lay their schedule out so that features land in alpha, and beta is solely for testing. In other cases the beta's may actually just be more like release candidates, so you might get a couple then a release.

[aznkid25]

The Add-on compatibility reporter 0.6 is incompatible again, which means I can't install the Stylish add-on. Is there a way to make the add-ons work without doing the about:config hack?

[+Gary7 Subscriber²]

The Add-on compatibility reporter 0.6 is incompatible again, which means I can't install the Stylish add-on. Is there a way to make the add-ons work without doing the about:config hack?

It will be made compatibale soon. Have patience.