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).'"
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.
I... have 6 tabs open right now and 29mb ram usage with the 1.1 release. Don't know if that is because the new release is so good, or yours is so bad, however.
The Tech Terminal
That's why i switched to Opera. the ram usage and responsiveness of the interface is great. it took a little getting used to, but i use Opera on my windows machine, safari on my mac, and firefox in linux. granted i got opera for $20 with the edu pricing.
Kyle
http://www.unlogikal.net/
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
While it's true that the "Mem Usage" in task manager can easily show much more memory than the program is actually using, an minimizing a program will make this number drop, the number it drops to is still not the accurate memory usage figure. You really want to go to View/Select Columns and look at VM Size, not Mem Usage.
VM Size is the actual amount of memory the program thinks it has, between whats swapped out and what is actually being used. Mem Usage can be higher than VM Size if memory was freed but not yet flushed by the OS, or it can be lower than VM Size if some memory hasn't been touched in a while and is swapped out to disk. Minimizing an application just gives Windows a hint that it should flush freed memory and swap out pages that have not been touched recently, which is why the Mem Usage figure drops when you do that.
Morphing Software
- right click link, "Copy link location"
- paste into URL bar
- press enter
Warning: This is illegal in the United States under the DMCA.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
bugzilla.mozilla.org/show_bug.cgi?id=131456 Memory use does not go down after closing tabs (resources not released) - Resolved:Fixed
These people look deep within my soul and assign me a number based upon the order I joined. -Homer Simpson
bugzilla.mozilla.org/show_bug.cgi?id=131456 Memory use does not go down after closing tabs (resources not released) Resolved:Fixed One of the many core changes that are going to be in Fx 1.1.
These people look deep within my soul and assign me a number based upon the order I joined. -Homer Simpson
Firefox's memory usage is part reason why I ditched it and went Opera mostly full time. (Of course, Opera's innovative features are hard to beat so that is why I mainly switched). Being on a really old machine, Firefox would often use 112 MB of RAM with only around two-four tabs open, now with Opera at that many tabs, It'd only use around 25 MB of RAM with the same pages open. When Firefox is started up with no pages open, it'd be around 21 MB of RAM or so, with Opera, it is only around 13-14.
- Teja
No need, in Firefox:
1. Go to about:config
2. Type "referer"
3. Set network.http.sendRefererHeader to 0
I wouldn't call it overwhelming Firefox (nor would I call it overhwelming Firefox). You probably have Firefox set to disable javascript from changing the status bar text. If you enable having javascript change the status bar text in options > web features > Javascript Advanced or if you completely disable javascript, the links show up fine in the status bar.
Fark formats its links like this:It uses onMouseOver to hide the click tracker from the status bar. The appropriate behavior for Firefox would be to show the actual url the link points to when you disable status bar text changing, so it's still broken.
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
The validity of the HTML is irrelevant - the bug was a type of bug known as a "reflow bug". Reflow bugs are timing-dependant, in that they only occur when things happen in a certain order. This is a large part of why people with fast connections were less affected by the bug. You could likely construct a page with 100% valid XHTML which would demonstrate the same bug.
My server