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.
Firefox 1.0 is very slow on google maps. Mozilla 1.7 is way faster, so are Firefox nightly builds. I wish there was a way to get Firefox 1.0 to work as fast...
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
The real question is wether it can pass the Acid2 test. Safari needed ~2 weeks to pass it. Firefox 1.1 is coming out like forever.
On a side note, if any FF developer is reading this: make it so that the download manager doesn't popup if you save _images_ (and other content which is already downloaded). Extremely annoying.
- 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
Whenever I load a PDF in firefox it hangs somewhere during the initilization of Acrobat. It also hangs equally as long if I leave the pdf, and having firefox 1.0x shut down the acrobat engine.
But if I launch Acrobat as a separate program and just have it sitting empty in the taskbar, Firefox goes through PDFs just fine.
A strange bug. A frustrating one. One I hope they catch.
The memory usage depends heavily on your browsing patterns (what you have open, what you had open, whether you use tabs vs. windows, etc).
My server
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
Preferences > Web Features > Enable Javascript > Advanced > Allow scripts to: [x] Change status bar text.
there's more than one way to do me.
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.
It's likely to be preloaded, especially since 'Web View' or 'Web Kit' or whatever the hell they call it is used in many applications now.
I also agree that Safari in Tiger is really superb and it's much, much better than Firefox for the stuff I use it for, which is tabbed browsing, popup blocking, intergrated google search and good standards support. I really like the RSS feature, and you can also change it to use a 3rd party app (eg: NetNewsWire) which is handy as the blue RSS icon saves legwork trying to find the RSS or XML icon on the page itself.
The trouble is that Mozilla is always going to be at a real disadvantage in the speed stakes, especially when you consider a) it's biggest competiton comes from the OS developers themselves, who can preload/optimize the kernel at a whim, and b) it was wrote as a full application runtime enviroment instead of just a browser, with much of the XUL stuff being useless with the advent of xmlhttprequest and good DOM support in major browsers.
Have you seen this stuff?
l ist.php?application=firefox&numpg=10&category=Kios k%20Browsing
m
l ist.php?application=mozilla&version=1.7&category=K iosk%20Browsing
http://www.mozilla.org/support/firefox/tips
https://addons.update.mozilla.org/extensions/show
http://tln.lib.mi.us/~amutch/pro/phoenix/kiosk.ht
http://malektips.com/firefox_0007.html
Maybe use moz instead
https://addons.update.mozilla.org/extensions/show
You might also want to vote for this:
https://bugzilla.mozilla.org/show_bug.cgi?id=3341
The Singularity is closer than you think
Quant
You can see the full instructions in Chase Phillip's weblog post.
be aware there are some webpages that'll scream if find you're blocking the referer
http://www.fanboy.co.nz/adblock/
I've been using Opera 8 Beta for several months now, no problems. I have 60 tabs open and it's using about 58MB of memory. It's really great.
For Ad-blocking I use Opera Ad Filter which is donationware and works great! However, you have to separately configure the ad sites to block; FireFox's right-click ad-blocking is much easier to use and wins here.
I've never had any CPU issues with Opera 8, and maybe 2-3 crashes in several months of use, but these kinds of interactions can be very dependant on what your system is running, and that's clearly different from mine.
When it crashes, as the parent said, it maintains the tab list and open sites and gives you the choice to resume from the previous saved session, start a new one or recall any old one. I have several saved sessions with pre-configured tabs that I like to recall when I am doing specific work online. This feature is awesome to me.
Opera 8 has always rendered Slashdot perfectly, unlike FireFox. It even feels faster than firefox, but I admit it's all subjective when feelings come into play. I've never scientifically benchmarked these two browsers.
Opera 8 also has a pretty decent mail and news reader built-in, that auto-learns your mailing lists, contacts and subject threads.
I just wanted to point this out because Opera 8 does not have "a long way to go" as the parent says.
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
Click "Bookmarks," "Add Bookmark Here," and check "Bookmark all tabs in a folder."
Actually that's not correct, the bug is only triggered when Gecko is in quirks mode. It is a browser bug but it can be avoided by using standard code.
I'm using the 1.0.3 for windows from getfirefox.com
Two windows, each with 8 open tabs, basically I started on slashdot in one window and randomly hit links for tabs, and started on my homepage in another and did the same.
So, 2 windows, a total of 16 tabs/pages, and task manager says I'm using 43M... Doesn't seem too bad to me...
If I restart firefox, 1 window and 1 tab is 23M, so you can complain about that maybe.