Recommended Posts

It is a pity that Mozilla is taking Chrome's ugliest GUI crimes (no status bar, WTF?) as a part of their "improvements".

Having to install add-ons to get back functionality sucks.

i don't mind no status bar, the problem is that extensions haven't all been ported over to toolbar buttons yet.

I've actually started to get used to the lack of a status bar. In reality, it only served four real purposes: a little hub for some add-on features, a place for the progress bar, current state of the site's loading process, and information on where a link leads on hover. Since it got converted to an add-on bar, that function was retained. The loading info got tossed into the tabs with the throbber icon. And the link info got tossed into the location bar, which is really nothing more than a change. Once I got used to it being there, it felt just as natural as it being in the status bar did.

Putting everything into the toolbar is ridiculous. Some things are just statuses, not tools.

Genuine question, not rhetorical: what kind of things are you thinking about?

Currently I have Xmarks, a zoom addon and firebug in my bar - Xmarks will soon be replaced by Sync (and I don't think it needs a status icon anyway), zoom controls are suitable for the toolbar. Firebug, like ABP, could also be suitable for the toolbar.

In terms of built-in stuff, I don't feel I'm missing anything in particular.

Putting everything into the toolbar is ridiculous. Some things are just statuses, not tools.

Everything should be a toolbar item, even if it simply shows a status.

But it's at architectural thing, it's something the end user will never have to care about (until they realise they can actually move them around, and they're not fixed like in previous versions)

Stylish works just fine on the latest nightlies if you just disable compatibility checking.

Add extensions.checkCompatibility.4.0b = false to your about config.

Thanks!

The only issue I still have is blurry text with hardware acceleration enabled.

Thanks!

The only issue I still have is blurry text with hardware acceleration enabled.

If you own an Nvidia card, remember to turn off Anisotropic Filtering (I think that's what it's called) for the Minefield executable using the NVidia Control Panel.

If you own an Nvidia card, remember to turn off Anisotropic Filtering (I think that's what it's called) for the Minefield executable using the NVidia Control Panel.

I do, interesting, I'll check this out.

I hope the other tab animations make it to Firefox 4. It'll feel outdated without them.

http://www.stephenhorlander.com/images/blog-posts/tab-animation/animation-tab-tear-off.html

Those are definitely incredible looking. Hopefully the UI and animations will be completed soon so we can have that in our hands. :D

Got a screenshot?

It may be that you just don't like how DirectWrite renders text.

It probably is that, the text just doesn't render as bold as it does in Chrome, or with Firefox and hardware acceleration off, screenshot in a bit.

It probably is that, the text just doesn't render as bold as it does in Chrome, or with Firefox and hardware acceleration off, screenshot in a bit.

Here's my comparison between firefox and chrome on my system

firefoxvschrome.jpg

Are you using GDIPP? The rendering in your Chrome screenshot points to it (the bad character spacing is an old GDIPP issue)

It doesn't looks like either screenshot is actually showing sub-pixel AA (even though it looks like it should be), but that might just be because it's a JPEG image (destroys the fine colour detail)

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

    • No registered users viewing this page.