Firefox 4 Beta 9 Out, Now With IndexedDB and Tabs On Titlebar
surveyork writes "''Mozilla today officially released Firefox 4 Beta 9 and it's a big improvement over previous betas and a parsec beyond the Firefox 3.6.x experience. At this stage, after months of development, Mozilla developers are clearly nearing the end of this development marathon.' After Firefox beta 9, a beta 10 and a single RC are scheduled (this road map can change, of course). The main features of Firefox beta 9 are IndexedDB and tabs on titlebar (just like Chrome and Opera). IndexedDB allows sites to store data on your computer (with your prior authorization). Tabs on titlebar is self-explanatory. Old-schoolers can always turn on the 'show menu bar' to get their familiar GUI back. Oh, and Fx beta 9 is fast and starts fast. Firefox beta 9 available here and in lots of official mirrors."
Does it have a status bar at the bottom?
If not, then it's still EPIC FAIL.
I just switched to Chrome from using firefox for the last what 4, 5 years? I gotta say chrome just seems to make sense. not trying to troll just saying.
$action = empty(PHP) ? backToC() : unset(PHP) ; "when the concrete cases are understood, the abstractions are readily
http://mirror3.mirrors.tds.net/pub/mozilla.org/firefox/releases/4.0b9 hasn't been hammered yet...
I really thought the final release would be out by now. Remember last year when Mozilla said they were moving away from big releases and adopting a fast release cycle with mixed bug fixes and new features? Whatever happened to that plan?
Cory Doctorow talking about cloud computing makes as much sense as George W Bush talking about electrical engineering.
Why is this touted as a feature/benefit? In Windows (7, specifically) when the window is maximized, the tabs are so flush with the top of the screen that it makes Firefox almost unusable for snapping (left, right, or down from top). I understand that pushing the tabs up save pixels - a scarce asset in netbooks - but are five or ten pixels so valuable that it's worth rendering one of the best features of Windows useless?
The more it copies Chrome, the less reason there is to use it, and more motivation to switch to Chrome instead.
I don't even use tabs at the top; I use tree-style tabs. Hopefully they'll still work.
In other news, I do like the status bar being visible. The primary reasons I don't use Chrome are the missing menu and status bars.
One thing that confuses me about tabs on top is that it implies that everything below the tab is associated with that tab. Ok, I get that part. I watched the video by Alex Faaborg and it makes sense.
But I therefore expect that if I rearrange any items below the tab, such as customizing the layout by adding or removing buttons or moving the home button to the right side, or resizing the size of the address bar versus the search bar, that those changes would be limited only to that tab and be sticky for that tab. That doesn't happen and visually it's confusing. All of those elements are grouped underneath the tab and when I switch tabs, the changes are there too. Huh? It's completely counter to what I was expecting and doesn't make sense. The only thing that changes from tab to tab is the text in the address bar.
I would think this would be very important due to the ability to save app tabs. I might want to save an app tab to a specific site and have the navigation toolbar customized a certain way just for that tab.
Note: I'm using beta8 and haven't upgraded yet so maybe this bug has been fixed.
Cory Doctorow talking about cloud computing makes as much sense as George W Bush talking about electrical engineering.
Now up to Firefox 4.0b9 and STILL you can't watch Flash videos with 64-bit Flash on 64-bit Firefox on Mac OS X. It's been two or three betas now since they broke this, and they just refuse to fix it..
In November 2010 they fixed a bug that was originally submitted in November 2000. That's Not a typo. 10 years ago. So just get in line and wait your turn.
As long as Chrome lacks NoScript, there will continue to be a reason for Firefox. Fix that dealbreaker, and all of the rest is negotiable.
As always, we've packaged it for portable use (USB, cloud drive, etc) which also lets you try it out right on your desktop without installing it and impacting your local Firefox install at all.
http://portableapps.com/news/2011-01-14_-_firefox_portable_4.0_beta_9
And it really is noticeably faster than previous released.
Portable versions of Firefox, GIMP, LibreOffice, etc
I'm using Firefox because I prefer it over Chrome and such. I don't want the layout changed every major release.
We are all God's parents.
Changing the default behavior is always bad. Always.
If that were true then you'd turn on the computer and get "C:\>" (or "$" as appropriate). Clearly absolutes are not so absolute.
What a complete and utter disconnection between summary and data, who the hell made this UI decision?
Seriously now, try to imagine a proper filing cabinet with the files containing the data, only the labels per file are 4" higher than each file, with stuff inbetween obfuscating and disconnecting the information?
Thank christ this stupid, stupid option is able to be disabled.
Furthermore, the status bar being on the address bar - ok I tried to like it, I tried not to be 'backwards' and old fasioned (as I am with classic UI in Windows) but I just can't do it, I like to see a huge, giant URL down the bottom - I want to see the full thing incase it contains something dodgy. I'm a tech, I need to know what I'm clicking - I find it an utterly stupid design decision.
Furthermore the performance is better but hardly sufficient, the performance is the only thing chrome has going for it in my opinion, sorry but I'm not going to bow down and love it just because it's googles product. Firefox has and continues to serve all I need in a browser, even then with a couple of addons ("tabs menu" - "tab mix plus" etc)
I will continue to adjust FF4, FF5, FF6 to look like FF3. (Oh and I'm not too old fasioned, the awesome bar is bloody incredible)
ALL firefox needs, the ONLY thing it needs in my opinion is speed, I have a quad core 64bit machine with 6gb of ram, I browse between 3 and 18 hours a day,.. I absoloutely don't care how much resources my browser takes, I just want the best performance possible, period.
Fuck copying Chrome, ugh - don't latch on to fads which are stupid but popular (see: white plugs on everything after the ipod, see: fucking glossy screens on laptops)
64-bit Flash ~is~ better than 32-bit because it's also the only build that's optimized to use the GPU rather than the CPU as part of the "Square" pre-release. But don't let your ignorance prevent you from commenting. Fucknugget.
You're ignoring the fact that it wasn't all that long ago when 480 pixels was the vertical standard. Hell, I'm not even 30 and I can remember CGA in all its 640×200 glory. So what if the resolution bubble burst and we're finally finding a happy medium? There's still plenty of reason to make an intelligent use of space.
MSIE: The world's most standards-complaint web browser.
Not really true. There are tons of little detail differences that favor FF over chrome.
It's a good thing that they're copying each others' best ideas; they're both still vastly different implementations, produced by very different teams, with different priorities, and will always have many differences.
We live, as we dream -- alone....
"It saddens me that the devs feel they have to do things like this rather than fix the much more serious issues the browser has..."
Such as... "Granted on the plus side I can finally use a browser that properly frees up memory after closing a shit load (80+ tabs) at once."
Are the memory gobbling instabilities of Firefox fixed in version 4? I have 12 tabs open in 5 windows now in Firefox 3.6.13, and Process Explorer tells me that Firefox is slowly demanding more and more memory, even when I am only watching Process Explorer, and nothing is happening in Firefox.
Eventually, the memory gobbling of Firefox reaches a limit, and Windows XP SP3 becomes very unstable.
I've filed bug several reports about that particular instability of Firefox over about 9 years, but the problem has not been fixed.
Those of use who need to do research on the internet often have many windows and tabs open. That makes the instability in Firefox much worse.
So this means that i won't open a new tab with mouse "middle" click by default. Cheers and goodbye.
http://userstyles.org/styles/42402 This Stylish style implements tabs on titlebar when window is NOT maximized. I think there's some talk amongst Fx developers about implementing this feature (tabs always on titlebar). Apparently, they worry about leaving some space for dragging the window, that's why they don't put tabs on the titlebar when not maximized. Might be relevant: https://bugzilla.mozilla.org/show_bug.cgi?id=572160
2019 is going to be the year of Linux on the desktop.
The oldest bugs in Mozilla are ~12 years-old (from Netscape times). There are quite a few 11, 10, 9, 8... years-old bugs. A curious case: There was a 2002 or 2003 bug about implementing 'Paste & go' functionality. That bug was abandoned for years, well, with lots of discussion going back and forth. Finally, the bug was closed as won't fix or invalid. Then, the GUI team asked in Reddit about what the users wanted. Paste & go was one of the things they wanted. A few months later, Paste & go was implemented. Now I want to see the faces of all those who argued for years that this feature was not needed/too complicated/etc. Of course, there was at least one extension that added paste and go to Firefox. Thank $DEITY!
2019 is going to be the year of Linux on the desktop.
I mainly use Firefox, but I prefer Opera's tab stacking to Panorama. As parent says, Panorama makes you leave the main browsing interface. I think it's a bolted-on feature and the bugs at bugzilla seem to confirm that suspicion.
2019 is going to be the year of Linux on the desktop.
The status bar can be hidden with two mouse clicks. Were people really having so much trouble with the "View->Status bar" option that the devs needed to take matters into their own hands?
Worse, they knew it was controversial and was going to piss off a lot of people but they did it anyway.
No sig today...
As long as Chrome lacks NoScript, there will continue to be a reason for Firefox. Fix that dealbreaker, and all of the rest is negotiable.
It does have a functionality that works EXACTLY like NoScript. Are you guys even trying?
Menu > Options > Under the Hood > Content Settings > JavaScript > Do not allow any site to run JavaScript
Now when you visit a site that needs JS, you have a "JS is needed" little icon right on the address bar. Click it, and you can whitelist that site for now, or for the future as well.
Under the same options dialog above you can do the same for plugins as well, like Flash.
I disagree.
Turn your argument on its head: If the controls are above the tabs, that seems to imply that they apply to all tabs. Does that mean that if I click "reload", all tabs should be reloaded? If I enter a new URL, should all tabs go there, since the URL bar is outside the tabs as well?
I would argue that actually interacting with controls is far more important than rearranging them, so their placement should agree with the latter, not the former.
So the seven of you with a netbook can have an extension or a FF version that optimizes the UI for netbooks. There are more real computers than netbooks; things should be optimized for real computers, and then people can waste their time making extensions to make it usable for netbooks.
Cairo isn't controlled by Firefox developers.
Different priorities, a lot was done.
Firefox has had a JIT for a few years now.
It's a draft and w3c urges against standardizing against the draft. The gap between HTML5 draft support and other browsers isn't really that significant from my observations.
Change is certain; progress is not obligatory.
There is a reasonable bit more to NoScript than simply javascript yes/no per domain.
java, flash, silverlight, can be blocked
audio/video, iframe, frame, font-face tags can be blocked
then there is clickjacking prevention and the Application Boundaries Enforcer
(Though some may not be necessary on Chrome I admit I don't know the ins and outs of it's in build security features)