Slashdot Mirror
Firefox 30 Available, Firebug 2.0 Released
Today Mozilla made Firefox 30 available, a relatively minor release after the massive redesign in version 29. According to the changelog, new features include VP9 video decoding, support for Opus in WebM, and horizontal volume control for HTML5 video and audio. Developers got support for multi-line flexboxes and hang reporting for background threads. There were also a number of security fixes. The Android version of Firefox received better support for native text selection, cutting, and copying, as well as predictive lookup for Awesomebar entries. The availability of Firefox 30 coincides with the launch of Firebug 2.0, which features an updated UI and a new debugging engine called JSD2. Significant new features include JavaScript syntax highlighting and de-minifying, improved code auto-complete, and the capability to hide or show individual Firebug panels.
...with this rapid release schedule. Firefox is trying to update more often than Java nowadays.
Run an unstable branch like everyone else, and run a testing/beta branch to become the next stable. It will make life a lot easier.
Do not look into laser with remaining eye.
Version 30? Pssssh. I've been using version 35 since it was released 5 minutes ago.
Edit: Oh shit they just released version 36!
If yes then I'm still not using it. Palemoon all the way.
Only the State obtains its revenue by coercion. - Murray Rothbard
Does it still require Classic Theme Restorer?
[Fuck Beta]
o0t!
The linked changelog and description are for Firefox 28. For FF 30: http://www.mozilla.org/en-US/firefox/30.0/releasenotes/. Even accounting for FF's release schedule and for Slashdot delay, that's a bit much. Only important change for me as an end-user looks to be:
Ignore autocomplete="off" when offering to save passwords via the password manager (see 956906)
I hope they fixed the memory usage problem I've been having since the last update. Lately for me FF has been running up over 3GB of memory usage and then crashing after anywhere from 6 to 12 hours with only 7 or 8 tabs open. It's been driving me crazy.
...if they used sane version numbers?
Probably something like 12.0.1...
Do not look into laser with remaining eye.
Yes
. . . its been broken for over a year.
Any chance we can have Firefox 3/Firefox 4 supported again and just forget about all these latest BS changes ? :-(
If I wanted something which looked and worked like Chrome, I would bloody well just use Chrome and have done with it.
Are there any non-mainstream browsers which supports the NoScript and DownThemAll/ImageHost Grabber and DownloadHelper functionality ? (That's a serious question, because if there are, then I intend to evaluate them.)
I've now got as many addons to restore traditional Firefox behaviour as I do to implement additional functionality. :-(
When does that usually get updated in Ubuntu?
Is Devmode back yet? Or alternatively, does SuperDevMode work correctly yet? I like Firefox as a browser, but can't test my GWT stuff in it.
If you are not allowed to question your government then the government has answered your question.
The feature that Chrome has where you can go forward and back pages by swiping left and right? I like that feature but I don't like Chrome enough to use it instead of firefox.
Tell me how to place the fucking tabs below the URL box.
Bless Firefox, and forsake them for hyped redesigns like these.
http://www.palemoon.org/
Switched from Firefox to Pale Moon because of Version 29 and haven't looked back. It is excellent.
If not, I'll stick with Chrome. Switched over after they removed the status bar.
Why don't they just randomize the user interface every time you start the program? I've spent over a decade getting used to things being in certain places with FF. Each version shuffles things like rearranging the furniture in a blind man's house. I have to put things back where they were so my muscle memory still works. I still go for View/Page Source - it's been that way for many years. Why change it? What does it accomplish to change it?
So, do the people who write this software not use it themselves? Do they not have muscle memory? Do they really re-learn where everything is every new release?
I mean, why? Why rearrange everything and trash the user interface? There's no reason for it. I don't understand. I can't process the idea that they just go in and trash everything for no reason.
I don't understand. I am not sure I want to understand. This is crazy, so should not make sense.
I just updated to Firefox 30 and two seconds after finishing the install, it crashed. Not a good first impression.
Try an add-on called "Tabs on Bottom"
I'm using it and it works as advertised.
Does anybody else see this behavior? I'm having some trouble where my Firefox is not automatically updating to v30. I checked all the forums, but I couldn't find anything that would make it work. Could it be due to the fact that I deleted Firefox from all my systems because v29 was a steaming pile of shit?
Most UI designers these days are hipsters. They don't give a flying fuck about usability. All they care about is making a UI that's trendy. It's totally cool if it's trendy but isn't actually usable. Usability is irrelevant to them.
Firefox is just one victim among many. They've fucked up Chrome from the very beginning. They've fucked up GNOME 3. They've fucked up Windows 8 and Windows Server 2012. They've fucked up iOS 7. They're in the process of fucking up OS X 10.10. They've been fucking up web design for a great many years now.
Hipsters are a disease that infects software projects. Once you understand that, then what has happened to the UIs of these formerly-great software projects makes perfect sense. It's much like the plagues that ravaged Europe centuries ago. A small hipster infection can spiral out of control and can destroy even the most robust and usable of software systems.
At the rate they're going, they'll probably emulate IE's look by version 40 (around next week)
I've got better things to do tonight than die.
I've noticed it's not just firefox that does this stuff. I can't even count how many times software or an OS has changed something for no reason, removed features for no reason, changed things randomly...at least give us the option to CHOOSE if we want this new feature or look. Don't remove features that I've relied on for years. I remember back when I was using Xubuntu, XFCE had the very nice feature of allowing you to change the default right click on desktop menu from the standard "create folder, file.." etc to a custom menu like fluxbox has. I used XFCE just for this feature and they removed it for no good reason. Just give us the CHOICE to revert to old ways if you're going to change it, ffs.
It's totally hilarious how almost EVERY SINGLE PERSON outside of Mozilla who has had to use Firefox 29 has totally hated its UI. The most positive responses I've seen so far have been from people saying that they only kind of hate it. For each response like that, I see hundreds more from people who absolutely, indisputably, completely hate it to its very core!
I think this is funny as funny can be. The Firefox UI designers have created something that's universally hated! It's not just a little bit of hate from a few people here and there. It's total, unmitigated, unrelenting hatred for the Firefox 29 UI! LOL!
My betting is that the top dogs at Mozilla have been paid handsomely to shutter Firefox and make the transition to Chrome as smooth as possible. Firefox has really been Google's project for a long time now, in financial terms, and they don't need it any more.
"Something strange is happening with my video streaming site." she says.
"Oh, I heard putlocker had their domain name seized." I say.
"No, that happened awhile ago, the video won't go into full screen now."
She clicks the full screen button and jack shit happens.
"Yeah, I did a dist-upgrade last night on your laptop, Chromium must of broke some shit, try Fire Fox."
"But Fire Fox is slow and everything moved around the last time you updated it." she says.
"I have to keep up with the security updates, you don't want to be using depreciated software. But yeah, these latest browser updates are bullshit I had to switch to something called Pale Moon."
When will these assholes learn? She doesn't give two fucks about what's cool and new, she just wants her shit to work and not be broken.
Firefox's share is plummeting
While I am not quite as vehement about it as you, I agree to some extent. Firefox has been trying to Chrome-ify its interface, and it sucks. It needs to go back to its roots.
And goddamn Google for harming it. Firefox is our last best hope for a non-intrusive, "independent" browser. Firefox needs to start looking -- HARD -- for better outside funding.
I have to wonder what they think makes all these updates worthwhile. This release breaks two-finger scroll and swipe when I open a couple tabs.
.
Unfortunately, the rabid [sic] release cycle seems to do little more than encourage the developers to make changes for the sake of changes, not for the benefit of the users.
Stop this insanity.
I'm at my Nevada vacation/retirement place for the first time since migrating my laptop from Ubuntu 12.04 LTS to 14.04 LTS. This dragged in Firefox 29.0 ("... Canonical 1.0").
The place only has dialup Internat at about 38Kbps. (Somewhat higher speeds are available at substantial cost, which doesn't make sense untlil we're here for more than a couple weeks a year.)
Web browsing was barely usable at this speed by using a few tricks. The most effective one was to configure Firefox to not load images until/unless I wanted to look at them.
When I got out here last Friday I discovered that firefox 29.0 no longer has the radio button in the preferences/configuration menus. An hour or so looking at about:config didn't turn up anything likely-looking, either.
Without this feature, "surfing" the current image-heavy web pages is essentially impossible. Even trivial pages may take a couple minutes to a half-hour to load. PER PAGE.
Did the Firefox crew restore the feature for 30.0? (Or does anyone know where it was hidden, if it still exists on 29.0 and 30.0?)
Developers breaking important features (that THEY don't use) while "improving" products is a real problem.
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
Palemoon
The "useless" toolbars are useful to people who understand toolbars. The pointless changes to the firefox UI are a big "fuck you" all the sane users.
Go use chrome if you want chrome. Some of us don't use chrome because the chrome UI sucks.
Did they fix the memory-hogging bug that causes instability? No.
Oh now, that's mean!
Is Firefox the Steve Ballmer (worst CEO) of browsers, the Zune of browsers?
Pale Moon Windows version
Pale Moon Linux version
Pale Moon has a 64-bit version. The 64-bit Pale Moon uses the Firefox add-ons; there are no problems except with some unusual add-ons.
I've been a fan for years, mostly because of the addons. Between the flakiness of the Android version and the chromification of the desktop browser, I think I'm in the market for something different. I understand the need to release security updates ASAP. But tossing in features and jacking up the UI every freakin month is a bit silly.
Hecubas
Can I just get the pre-3.0 interface back, please?
Along with the pre-"Awesome Bar" URL bar? All of the addons I've seen that purport to restore the old behavior fail to actually do it.
I can't recall a good UI decision made by the FF team in years.
Captcha: futility
I use firefox on an atom netbook with 2GB of RAM, with 20-200 tabs open at any given time. I occasionally debug javascript as part of my work activities, so I have a ton of web development plugins installed, plus a tab tree plugin, plus SQLite Manager, and then of course NoScript, Adblock, etc. I'm using Crunchbang Linux, and Iceweasel 30 from Debian backports.
If you have the time, you may want to try some debugging, because this is not quite the most limited x86 machine sold in anything that we might call recent history, but damn close to it. Performance has never been an issue. Good luck.
Those who advocate genocide deserve every protection afforded by law, and none afforded by common human decency.
An alternative would be to use Tree Style Tabs, and placing the tab bar on the side of the screen. I find it answers quite well, and I didn't notice the tab UI change. I have a habit of opening a bunch of links from e.g. a wikipedia page, browsing each for a while, perhaps opening deeper links, and then wanting to close the whole tree. If you think that might match your browsing habits, give TST a try.
Those who advocate genocide deserve every protection afforded by law, and none afforded by common human decency.
Why do they release Firefox 30 for Android in the Play Store BEFORE it is even on their own FTP server
Life exists outside of Google, you know...
Move Sig. For great justice.
The memory-hogging bug has been there for more than 8 years. The fact that it is not fixed indicates something about the management of Mozilla Foundation.
I just looked at the users statistics for Classic Theme Restorer. I'd think an increase of 7962% in users from version 28 to 29 would suggest a good chunk of the Firefox user community doesn't in fact like the new UI. Granted that's not the entire userbase, but the number of people using the addon is still increasing.
My guess is that 5.0[sane] would be around the time they changed the extension system (ca. 10.0[insane]) to take into account the rapid release cycle breaking extensions that relied on a max version number. Internally, I can't off the top of my head think of what changed internally since 10.0[insane], but I'd guess the introduction of Australis (29.0[insane]) would make it 6.0[sane] (unless there was another really major change which would push the sane version number to 7.0 or even 8.0). So FF 30.0[insane] would be 6.1[sane].
Another way of doing it is that the major version number only changes when an ESR is branched off, and the minor version number corresponds to an insane-major-number. So 4->4, 10->5, 17->6, 24->7, so 30.0[insane] would be 7.6[sane].
Perhaps if we can work out what version number Firefox should have, we can encourage disgruntled Firefox users to refer to it by it's sane version, and hope this will catch on.
Why are slashdotters so angry about the release schedule? Isn't this what is supposed to happen? According to ESR, release early, release often (and listen to your customers) is what makes open source great.
Is it really the release cycle, or is it that you feel that Firefox isn't listening to its customers. And who are the customers, really? The extension developers, or the people that use it on a daily basis to surf the web?
In my opinion, the customers are the people who browse the web. And if I look at it as that kind of customer, I am quite happy with Firefox and its release schedule. I get updates automatically and often and they often make the browsing experience better. Sure, sometimes something breaks, but they are keen to fix many of these problems.
-- The Internet is a too slow way of doing things, you'd never do without it.
Oh crap, another of those releases that forces us to go back to rewrite existing pages.
We require the password autofill to be off, because the password is only used for the first login. Afterwards, a system based on unique per machine (and user) keys take over.
Inquiring minds want to know...
Opinion:=TMyOpinion.Create(Me);
OK, here's the deal. I've been on FF since it was called something else and version number was 0.2. I'm still loyal but am getting increasingly annoyed and have to revert more and more things each version. Here's the rundown this time:
1. The FF29 and FF30 GUI is crap. The previous one was superior in every aspect. That panel thing you get by clicking the "hamburger menu" is a mess that I won't even try to decipher. Curved GUI elements are inane on a rectangular display. The background tabs are hard to tell apart, the borders between them suck. Just get the old theme restorer add-on to fix all this stupidity.
2. FF29 and FF30 crash every 20 minutes with HTTPS-Everywhere add-on installed. It took me a while to figure this out, disabling Flash or Hardware Acceleration etc. has nothing to do with it. That add-on has to be updated, although I don't understand why the problem crept in with FF29+.
3. The changelog in this article is for FF28. WTF Slashdot? The correct changelog is at http://www.mozilla.org/en-US/f.... It has nothing to do with VP9 or HTML5 or Opus. Firebug 2.0 compatibility is accurate however, so the summary is a hodge podge of FF28 and FF30 changes. But I knıow why, because it's getting icreasingly difficult for Mozilla to post a damn changelog on time. It takes about 1-2 days after the update gets pushed out before a damn changelog appears for the actual version.
https://dalgamotor.wordpress.com/ - Elektronik beyinlere ozgurluk asisi (Turkish)
for many months had crashes regularly multiple times per day. enough is enough. ppl @ ff manage to kill it. shame on u fagots.
The problem in Firefox is not sensible memory usage. The problem is that the memory-hogging bug is associated with instability in Firefox. It's a serious defect, unplanned use of memory.
Classic Theme Restorer fixes some of it. But really, should the end user have to fight the developers so hard?
The developers don't want me as a user. That's clear. They've got their middle digit right in my face.
Should I struggle to keep using the software they so clearly want only *other* people to use?
Yeah. I don't get what he/she is on about either. Saying "I like the toolbars that used to exist" is not dictating to Mozilla about some "one true way" to use a browser. It's the opposite! It's celebrating features and choice.
The ones dictating the "one true way" are the new breed of Mozilla devs, the ones that take stuff away from their users and claim that as an advance.
I can't think of anything more insulting as an end user of a product than to be told that the reason I'm using some software is so stupid that it's being taken out.
So, my return riposte to the Mozilla devs has to be: I don't need you and your childish dumbed down browser. I will use a different one, one that still works properly. Goodbye.
Seamonkey remains un-ruined, as usual.