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/
Sounds something like the "Private Browsing" feature in Safari.
Dashboard Widgets
So, how about that Firefox "feature" that keeps dynamically grabbing RAM as new images are displayed (at least that is where I am seeing it). Being a weather guy with my image looper adding new images every 5 minutes (and deleting the oldest one; the memory still isn't given up), I hate to see my browser using 500MB of RAM after a couple of hours. I was able to fix it with an entry in about:config called browser.cache.memory.capacity, but it would be nice to know if it is fixed by default since we will be rolling out Firefox on a bunch of desktops where I work in a few months.
Bryan R.
The price of freedom is eternal vigilance, or $12.50 as seen on eBay.....
The Tiger version of Safari truly does load faster than Firefox now (this must have been a priority for Apple!) ... not sure if it's preloaded like IE is but it is quick now. Generally though Firefox is jus a better and more convenient browser.
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?
Bugzilla has banned links from slashdot.
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.
Might be related to http pipelining being enabled or disabled on one of your installs. It makes a HUGE difference in the speed all those little tiles load for me.
Morphing Software
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
I think there are a few setbacks, UI wise, in the latest builds.
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 . . .
- 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
Did you report it along with your fix? Because not everyone uses the image looper quite that much and this could slip through the cracks without someone pointing it out.
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?).
Quack, quack.
Will it support ActiveX?
See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
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 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
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
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.