Slashdot Log In
Firefox 1.1 Boasts New Features
Posted by
timothy
on Sat May 07, 2005 06:52 PM
from the on-a-roll dept.
from the on-a-roll dept.
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).'"
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
What I'm curious about (Score:5, Interesting)
(2) Does it finally start to reverse the recent trend for firefox to become a huge RAM hog, or does it continue this trend?
Re:What I'm curious about (Score:5, Interesting)
Parent
Re:What I'm curious about (Score:5, Informative)
Parent
Re:What I'm curious about (Score:3, Informative)
Re:What I'm curious about (Score:5, Informative)
Parent
Re:What I'm curious about (Score:3, Interesting)
Mine is presently using 229MB. Of course, my X server is presently using 303MB, which, together is more than the amount of physical RAM that I have. Does Firefox map the video RAM into its address space?
Re:What I'm curious about (Score:5, Informative)
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.
Parent
Re:What I'm curious about (Score:4, Informative)
Parent
Re:What I'm curious about (Score:4, Interesting)
You have that complete bass ackwards. Memory usage shows how much physical memory (something which is usually somewhat limited) is currently allocated to the process, while VM Size shows the virtual memory (something which is practically limitless).
If a process starts up, allocates 100MB, and then never touches it, the VM Size will be significantly larger than the real memory usage, and in the real world this makes a big difference - having some seldom-used space in a paging file set aside for a task is a lot less relevant than having a block of physical memory set aside. If, on the other hand, a process allocates 100MB and then perpetually scans through it looking for Waldo, it won't be paged out and it'll consume real physical memory.
Of course memory usage can include shared memory blocks, but overall it is the best indicator of the real, practical memory usage of an application. No one cares how many new statements exist in the code - they care how much finite physical memory is practically used by the app.
Parent
Re:What I'm curious about (Score:5, Informative)
Parent
Re:What I'm curious about (Score:5, Interesting)
Parent
Uh-oh (Score:5, Interesting)
Maybe I'll see if I can send some info to the developer... It's such a useful extension. But I've never seen FF fly like this.
Parent
back/forward (Score:5, Informative)
And back/forward can cache the rendered layout instead of having to re-render everything: http://www.mozillazine.org/talkback.html?article=
Re:back/forward (Score:5, Interesting)
YES! Finally!
Instantaneous back/forward (with mouse-rocker) navigation is one of the major killer features that has kept me using Opera as my main browser for years now. And if the tab switching and general snappiness of Firefox v1.1 has also improved to Opera's level, as some attest, then I can ditch Opera for good...
Yep. That's it. I can live without the rest of the kitchen sink.
Parent
If it's about what we can expect... (Score:5, Informative)
Umm Sanitize (Score:5, Funny)
Re:Umm Sanitize (Score:5, Funny)
Yes, but it won't hide your posts on Slashdot from your girlfriend.
Parent
Re:Umm Sanitize (Score:5, Funny)
Yes, but it won't hide your posts on Slashdot from your girlfriend.
I have a hard time believing that that will ever be a problem for anybody, anywhere, ever.
Parent
Re:Umm Sanitize (Score:5, Funny)
I know what you mean. I usually imagine them with other girls.
Parent
Re:Umm Sanitize (Score:3, Funny)
Re:Umm Sanitize (Score:5, Funny)
Parent
Does the status line work properly now? (Score:5, Interesting)
Re:Does the status line work properly now? (Score:5, Informative)
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.
Parent
Another "hope they fix this" post. (Score:5, Interesting)
Re:Another "hope they fix this" post. (Score:5, Interesting)
Parent
Funnyfox (Score:5, Funny)
Copy? (Score:4, Interesting)
Sounds something like the "Private Browsing" feature in Safari [apple.com].
"Private Browsing" and "Sanitize" (Score:3, Insightful)
I'm sure people will use these new features to protect sensitive data and whatnot... but come on... most folks will use this new browse mode to keep their filthy habits on the DL .
Kill IE7 before it gets going (Score:3, Insightful)
My wife is an exclusively Linux user, and she does business with Candle-Lite. Unfortunately, their site is rife with IE-only garbage which makes it impossible for her to submit her orders online. If more people were using standards-compliant browsers, we really wouldn't have situations like this to begin with.
-AT
How About That Memory Leak, Fixed? (Score:5, Interesting)
Cool thing about OSS projects is I can ask you... (Score:5, Insightful)
I'm sure they'd like to have as much working flawlessly as possible, so they'd probably really appreciate this kind of feedback. I'll assume you did report it (or at least verify someone else already had) and leave it at "this is the beauty of OSS" even the users have their part in the process (is IE displaying PNG's or CSS properly yet?).
Parent
Safari's builtin RSS reader and Firefox (Score:5, Insightful)
There's only *one* area where Safari truly has a usabilty edge and that's RSS. The reader is *really* nice. Mozilla/Firefox could do something similar by improving Sage marginally (the article length slider is all that's missing it seems).
Is better syndication support (rss atom etc) being considered?
Ridiculous (Score:5, Informative)
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
/. Rendering (Score:3, Interesting)
Pornzilla (Score:3, Funny)
Pornzilla lives!
A few setbacks, UI wise (Score:5, Interesting)
The new preference dialog sucks. I suspect it's design is an attempt to match what OS X users expect, since Firefox devs have this (IMHO) crazy notion that the product should look as identical as possible across OSes.
The whole thing looks much more cluttered, and it has the same bugs that the UI did in pre 1.0 where the text was rendered inside of windows all the time (Like in the toolbar customization pallete, or in the current prefs). Which makes me worry that actually it's an XUL problem. If text placement is a thing that's hard to get right in XUL, it makes me worry about it as a platform.
However, performance did increase noticably for me, and the sanitize feature could be handy. I don't offhand find it much more useful that the "Clear All" button under privacy now. But it is nicely customizable, and not loosing my login cookies is kinda nice . . .
The REAL news: Firefox 1.03 remote .exe execution (Score:5, Informative)
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
/. bug (Score:5, Insightful)
Re:/. bug (Score:5, Informative)
Parent
Thing about FireFox I don't like... (Score:4, Interesting)
1.) If I hit the middle mouse button and use auto-scrolling for something like this slashdot page, Firefox will use 30 to 40 percent CPU. And I wouldn't classify my system as slow(Athlon64 3200+ w/512Mb of RAM). Hopefully the can do something about this.
NOTE: Prior to making this post, I observed that IE holds at around 7 percent for the same action.
2.) Unexpected browser closing in v1.01 and above that wasn't present in the pre-v1.0 releases, such as when I'm holding down several keys or typing something in the browser and then switch to another page with the mouse, causing the browser to close (or crash, though I don't get an error message).
The big question is... (Score:5, Funny)
URL history sort in address bar (Score:4, Interesting)
Some good and some bad (Score:5, Informative)
- 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.
Re:Some good and some bad (Score:5, Informative)
Personally I agree with the hate, but not the placement - give them to me on the left or the right, and leave more vertical real estate. But see below.
Live preferences: I hate these things with a passion... They already moved it to the Edit menu a while back (WTF?)
I'd prefer no live prefs, too.
But, the deal here is being consistent. They're trying to make the app work like other apps. So, the theory goes, even if they don't make your personal favorite UI choice, at least you know what it will do.
The Edit->Preferences thing is a long standing Mac standard from the pre-OSX days. Back then, most apps followed it. The strength of the convention was most noticable when you used a Microsoft app, which hung them off of Tools->Options. If you haven't noticed, non-OSX MacOS is where a lot (but obviously not all) of Gnome's UI sensibilities come from.
So, I generally agree with your behavioural preferences, and weirdos like you and me and always dick with the undisplayed options in the config file, fiddle with the chrome, etc.. Meanwhile, everyone else gets consistency. Which is a good thing.
Parent
Re:Rendering Bug? (Score:5, Insightful)
I've been using the nightlies and haven't had a problem with Slashdot for a while.
That said, if you really do feed a copy of any slashdot page to a web validator, it comes up with 100+ errors. The problem is that direct linking of Slashdot to validators have been banned by Slashdot maintainers.
Parent
Re:Rendering Bug? (Score:4, Informative)
- right click link, "Copy link location"
- paste into URL bar
- press enter
Warning: This is illegal in the United States under the DMCA.Parent
Re:MOD PARENT UP (and another suggestion) (Score:5, Informative)
1. Go to about:config
2. Type "referer"
3. Set network.http.sendRefererHeader to 0
Parent
Re:google maps (Score:5, Interesting)
Parent
Re:erm (Score:4, Informative)
Parent
Re:Acid2 (Score:5, Informative)
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/ [mozillazine.org]
Parent