Slashdot Mirror
Mozilla Firefox 1.5 Beta 1 Released
elfguygmail.com writes "Firefox 1.5 beta1 is out! It includes many new features including a new automatic update system, reworked options dialogs, faster browsing, new error pages, memory and stability updates. Get your beta at Mozilla.org."
Yeeeeeeah ! Faster back and forward means better performance reading messageboards . Deerpark alpha wont start on my machine. I am one those that submitted a couple of bugs on this. Good job boys!
Posting on it now. Generally teh snappier on OS X, which I appreciate. Text handling still isn't good enough to switch from Camino. The drag n drop tabs are a very welcome addition. Also, it looks like the Slashdot bug has been cleared up. Sweet.
The Rise and Fall of Online Community
For those here that run Windows in the Classic theme, here a link to info on how to fix the menu looks http://kb.mozillazine.org/Firefox_windows_classic
:(){
Warning, seems like most extensions won't work from 1.0x to 1.5beta1..
There are two things I am not fond of with the current non-Beta Firefox. The first is the way it needs to download the whole installer just to update a point release. The second is how extensions with similar functionality are not coordinated.
Take the GoogleBar for example. When I first installed Firefox it didn't come with a usable search tool, so I had to find GoogleBar which approximated the functionality of Google's IE GoogleBar. Now, Google comes along and releases their GoogleBar for Firefox and I'm left having to uninstall the old toolbar and install the new one. I'd rather the two projects just work closely together so that it could be updated seamlessly in one fell swoop.
Things like these occasionally mar my Firefox experience which is otherwise very smooth.
Speaking of smooth, does anyone else get a brief (1 second) pause when loading large pages in Slashdot? It seems to load part of the page, then it freezes for a second, then renders the rest of the page. It also happens on Photo.net, but there the whole discussion page reloads itself after loading once. Just a strange thing I noticed about Firefox.
Jesus saved me from my past. He can save you as well.
When installing Firefox 1.5
(1) Backup your old Firefox 1.0 profile
(2) Start with a clean profile, its best to use a clean profile
(3) Update your extensions
(4) If the extensions still complain, try this following the directions from this link
http://www.fanboy.co.nz/adblock/
"I'm patient, but will all of the developers make and re-make their extensions for every version?"
No. Developers will only have to test their extensions to make sure they're not broken by the latest Firefox release. All they have to do if their extension still works is tweak a version field at addons.mozilla.org (or wherever their extension checks for updates) and Firefox will allow the extension to run.
We're still at beta and that gives developers quite a bit of time to get their extensions certified against the upcoming Firefox 1.5 release.
If the extension author was relying on Firefox application code that changed, and broke the extension, then the extension will have to be updated.
I'm hopeful that most of the popular extensions will have certified against 1.5 or made updates available by the time 1.5 final ships.
- A
See: Mozilla SVG Update and Mozilla SVG Status for some more info.
- Allen Pike
Altering time, one time at a time.
Put the following line in your current version's user.js to get rid of the popups.
user_pref("browser.xul.error_pages.enabled", true);
Yup, just open install.rdf and change 1.2 to 1.6a2 and most extentions will work fine. The only one that isn't working for me is bugmenot.
"It is not how things are in the world that is mystical, but that it exists." -Ludwig Wittgenstein
I've been using the nightly branch builds for some time now, and no... I've seen no apparent fix for the memory leak. I mean, maybe a few holes have been plugged... but it still takes more memory than one would expect. On the other hand, I don't remember them claiming it fixed.
The best feature for me is the new automatic nightly version system using Firefox's update system. No more manually downloading, unraring, and changing folder names... just a few clicks and I'm done. A very big plus, for nightly users.
And since 1.5a may break a whole lot of extensions, I recommend Nightly Tester Tools, which can force an extention to work. You may also try going into about:config (type that in the URL bar) and manually making the entery:
app.extensions.version
Then setting this to a value of 1.0+. Can cause other problems though, so I'd go with Nightly Tester Tools first. Lastly, you could simply open the extension with an unzip util and modify the install.rdf, perhaps the most time consuming but failsafe method.
Works just fine if you go directly to the swf, but attempting to load it in a webpage does nothing.
For example:
This swf loads.
Its containing web page shows nothing. Works in 1.0.6
I mean, that's why this is a beta, clearly something is wrong. Shame though, I was hoping to use this on a daily basis to QA. No flash means I can't, I do too much work in flash to not have it load.
Yeah, it does. The adblocker's called PithHelmet. There's dozens of other extensions available, most of very high quality.
This, however, is solved in Firefox 1.5.
Now, when Firefox notice there's an update available, the user gets a dialog telling there's an update, asking "do you wish to close Firefox and install it now? (otherwise it'll install next time you start Firefox)"
Beware: In C++, your friends can see your privates!
No, this still doesn't fix bug #154892: "Splitting Absolutely positioned frames not implemented - Missing second page of content when printing or print previewing this site"
9 2
This bug prevents many web sites from printing in any useful respect from Mozilla browsers.
Its existence keeps me from rolling out Firefox as the default. It probably keeps any organization that frequently prints web pages from considering Firefox.
But what really irks me is that this bug has existed since 2002!. The bug has been duplicated in dozens and dozens of bug reports. It has at least 70 votes in Bugzilla. Yet no one has fixed it, and there is NO INDICATION that it will be fixed in the foreseeable future, yet it directly affects the user's browsing experience.
The history and severity of this bug does not reflect well on the Mozilla browser or its open source development model. NOTE: I am actually, personally, quite impressed with the Mozilla project, but someone who wants an excuse to banish free software might start with something like this.
Finally, as a Firefox user, a personal plea: Somebody, please fix this! Please?
For more information:
https://bugzilla.mozilla.org/show_bug.cgi?id=1548
1.) OS X builds of Firefox 1.5b1 are _much_ more stable than their 1.0.x cousins. If you take a look at the URL below you'll see a great big stack of bugfixes, including many for OS X.
5 b1.html
http://www.squarefree.com/burningedge/releases/1.
2.) That sounds like an issue with JavaScript menus - I doubt it's the browser's fault per se; it could be an issue with the way the menu is designed.
SCREW THE ADS! http://adblock.mozdev.org/ Proud user of teh Fox of Fire - Registered Linux User #289618
Too bad the guy didnt know about the "View Formatted Source" Extension for firefox (Bigger shame since he is a part of the mozilla foundation). http://www.extensionsmirror.nl/index.php?showtopic =3565
Enjoy.
Rahul
Well, there goes my karma, I WILL be modded as troll for this, but had to get it out
It doesn't open in a new tab, but the current tab (as you'd expect).
Have a look at this error screen for an example. I'm on XP at work, but I would think that other platforms would be similar.
Firefox, by the way, will fall back on the cache if it's unable to get the HEAD request. I'm not sure if it will correctly fall back if the HEAD succeeds but the actual request does not. IE will crap out, though.
Precisely what the "correct" behavior is, by which I mean "what the user expects" will vary from case to case, so it's hard to have a case that everyone agrees with. Netscape and IE both implemented what they thought was right, and have retained that behavior for consistencies sake even though some of the purists in the standards bodies have changed it.
Bug 9458 - Implement inline-block in layout.
https://bugzilla.mozilla.org/show_bug.cgi?id=9458
This is one of those golden-oldy bugs with a 4-digit bug number, so chances are it's really hard to implement.
Opened: 1999-07-08 15:25 PDT
Last modified: 2005-09-06 12:46 PDT
It looks like you might be able to get away with using both of the following rules:
display:-moz-inline-box;
display:inline-block;
Get Firefox!