Slashdot Mirror
Firefox 1.1 Boasts New Features
Distro Jockey writes "The Fedora Core Blog gives a review of the features we can expect from Firefox 1.1. Many uses have been running the latest trunk builds and seeing dramatic improvements in page rendering, managing many tabs quickly, and the much-anticipated fix for the /. layout bug. From the article: 'One major new feature in Firefox 1.1 is the "Sanitize" feature. This enables secure browsing with much more ease. Select the "Sanitize" option in the preferences and Firefox will scrub your profile of sensitive information (which you select in the preferences).'"
(1) Does it finally fix that bug where sometimes images from certain hosts will stop displaying until you restart Firefox?
(2) Does it finally start to reverse the recent trend for firefox to become a huge RAM hog, or does it continue this trend?
And back/forward can cache the rendered layout instead of having to re-render everything: http://www.mozillazine.org/talkback.html?article=
Morphing Software
...it's called preview, not review.
So this will clear all my tracks automaticly when I, say look at the hardcore of porn?
Try hovering over a link in fark. It seems the text to display it is so complex, it overhwelms Firefox.
I for one hope that the MacOS X version properly supports the middle mouse button (apparently the nightly builds have before the 1.0.3 release, but that release doesn't). Additionally, I hope it also uses Emacs key bindings.
-- $SIGNATURE
http://www.funnyfox.org/
This isn't really so much a review as a description of features currently in the nightly. Firefox 1.1 isn't expected until June at the earliest. The roadmap (http://www.mozilla.org/projects/firefox/roadmap.h tml) gives a rough overview of the timeframes involved right now, though it is not always accurate as it isn't updated frequently.
/. crew. Yes, an incredibly fast back/forward feature has been checked in to the latest nightly builds, but what they won't tell you is at present this feature is DISABLED. While that doesn't mean it won't be enabled in the future and might be enabled for 1.1, as it stands this feature is off by default and only accessible through a custom pref, so in its current state it changes nothing for the average end-user.
7 66
Honestly, Firefox 1.1 isn't even in alpha-release yet. To take some highly unstable code and to "preview" it is a bit premature right now. I would call 1.1beta a better time to 'preview' things, as hopefully by then there will be a feature freeze and things will have stabilized a bit. I'm not kidding about the unstable bit either: up until a couple days ago themes and extensions wouldn't install in the nightly builds.
In fact, an article like this does a disservice because it's misleading the
This forums post gives a better idea of the new features to be expected in 1.1 with one line sentences: http://forums.mozillazine.org/viewtopic.php?t=257
wait for the spyware slags get hold of this one
full remote execution of an exe with no user interaction
http://www.securityfocus.com/archive/1/397747/200
catching up with MSIE
The Good:
- Back/Forward Cache: Yes! Yes! Yes! This brings Firefox one step closer to the way I feel caching should be done. Back/forward should always pull pages from the cache (ignoring meta expire), and clicking links should always load the page from the server.
- Interface speedups: Great news. I love Firefox's rendering power, but the UI is slow as hell. This should help.
- Rendering errors fixed: More good news. While I can count the amount the number of times I've seen the Slashdot bug on my hands, better rendering is always a good thing.
- Focus follows mouse: One of the best changes. I've had so many issues with the focus not being where it's supposed to be. For example, I'll switch to another window or tab, but the focus is usually still in the old one. If this gets fixed, I'll jump for joy.
- Sanitise: More privacy == A Good Thing.
The Bad:
- Preferences tabs at the top: I hate having tabs at the top--I'd prefer them on the bottom (the sole reason I installed TabBrowser Extensions was to get the browser tabs to appear on the bottom), but I don't mind them on the left side. But having them on top is just horrible. It looks prettier on the left too, especially with my theme, which places an image of a gecko in the background of the left pane. I'm also worried that my theme won't work with 1.1--I've been using an old version of the theme, as the author made a change a while back that uglified the icons, defeating the purpose of the theme (the version I use only uses two colours in the icons...). Officially, my theme only supports up to 0.9, but I've hacked it to allow 1.0 to install it--if 1.1 has any major UI changes like this one, it may cause my theme to choke.
- Live preferences: I hate these things with a passion. I like to be able to dick around in the preferences and not have to worry about screwing something up. It pissed me off to no end back when I used Galeon, and it'll piss me off in Firefox too. But, hey, I can tell that the Firefox devs have an agenda to screw up the preferences dialog as much as possible. They already moved it to the Edit menu a while back (WTF?), they already flipped the OK and Cancel buttons, and now they're adding these shitty changes too. If I wanted to use a browser with Gnome's horrible HIG, I'd use Epiphany.
I support the Center for Consumer Freedom
No need, in Firefox:
1. Go to about:config
2. Type "referer"
3. Set network.http.sendRefererHeader to 0
http://weblogs.mozillazine.org/roc/archives/2005/0 4/acid2.html
... they're simply wrong, as anyone can tell by looking at the huge number of standards compliance bugs we fix in every release. And keep in mind that if everyone's #1 priority was always standards compliance, Firefox would never have happened. -Roc
There's been lots of speculation about which browser will get Acid2 working first. I'd put my money on Safari. The problem is that we're late in the Gecko 1.8/Firefox 1.1 release cycle and there are a couple of bugs that would be quite a lot of work to fix, and introduce significant risk, and they're just not as important as other work that we have long planned for 1.8 and some other strategic work that I'll blog about soon. We will get to it in 1.9.
I'm sure some will seize on this as an opportunity to say "Gecko developers don't care about standards"
Part 2
Use about:config to modify browser.download.manager.showAlertOnComplete
http://mozillazine.org/misc/about:config/
These people look deep within my soul and assign me a number based upon the order I joined. -Homer Simpson