Slashdot Mirror
Firefox 27 Released: TLS 1.2 Support, SPDY 3.1, SocialAPI Improvements
jones_supa writes "Mozilla has released Firefox 27 for Linux, Android, Mac, and Windows (download). One of the big changes is enabling support for TLS 1.1 and 1.2 by default. Firefox 27 also supports the SPDY 3.1 protocol. Developers got some new toys: support was added for ES6 generators in SpiderMonkey, the debugger will de-obfuscate JavaScript, and style sheets can be reset by using all:unset. Mozilla also announced some new social integration options. In addition to all these changes, the Android version got some UI improvements and font readability upgrades. For a future release, Mozilla is currently testing a new approach for Firefox Sync in Nightly builds. They recognized the headaches involved with how it works, and they're now opting to use a simple e-mail and password combination like Google Chrome does. In the old system, users were forced to store an auto-generated authorization code, which, if lost, would render their bookmarks, passwords and browsing history inaccessible. "
I sincerely hope these are optional and not going to get rammed down our throats so Mozilla can collect more ad revenue.
Because, quite frankly, I have no interest in having my web browser trying to integrate with social media.
Lost at C:>. Found at C.
I want to see WebPayment lift off. This could be a huge enabler for small internet businesses. Any news on that?
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
I used Chrome for quite a while but just switched back to Firefox. Chrome restricts things like downloading media (especially from YouTube) and doesn't work correctly on some ecommerce sites that I use. Firefox isn't (subjectively) that much slower than Chrome any longer and clearly has the widest choice of add-ons.
Maybe it's me, but Firefox 26 would crash at the drop of a hat
Tried running it in "safe mode" without addon's and see how that goes?
Firefox still crashes for me when it runs out of memory due to buggy javascript in either an addon or on a page. For example we use FinalBuilder at work, and the build control page has a massive memory leak in the javascript (sucky dom handling in web 2.0 crap) causing FF to run out of memory if I leave the page open over night.
Other than that it's been very stable on all the machines I've used it on for many years now (and that's both Windows and Linux).
Chrome uses almost 300% more ram than FF or IE 11 on my system when I have +40 tabs opened.
Tomshardware.com did some benchmarks that can confirm this. It even hit slashdot that FF 13 used the least amount of ram a year and a half ago.
FF 4.0 != FF 25 and later and a lot has changed since 2011. I am tempted to switch back to Firefox as it is so light and quick now.
http://saveie6.com/
What we really need is "Firefox Classic": a maintainable fork that takes the Firefox code base and strips it down to the essentials, without social networking add-ons or any of that garbage. Sort of like how Firefox itself originally forked off of the Mozilla Application Suite, come to think of it.
Am I the only one who could care less about social media integration?
One of the biggest changes in Firefox was that JavaScript was permanently enabled.
But a side effect of the removal of "Enable JavaScript" checkbox was the removal of the "Advanced" button which limited what scripts could do - move/resize windows, bring windows to front/back, allow scrpits to write to status bar, disable context-click (right click), etc.
Which is annoying because those options were good to have - especially sites that disable right-click.
On Firefox, it's possible to re-enable right click if you hold down Shift then right-click - this will force Firefox to display the proper right-click menu. But that's a PITA
While extensions like NoScript work, they don't prevent permitted sites from playing around with stuff like that - a site needs javascript ot work and then they promptly open a bunch of windows or disable right-click while it's enabled.
I'm not sure a "Classic" version would help much, it's the Internet itself that's bloated. You can have the fastest browser ever, but you're still downloading all that social media crap with Javascript pulled from all corners of the globe. The fastest web browsing experience? Firefox with Adblock and NoScript.
http://en.wikipedia.org/wiki/D...
"Mozilla Firefox via add-on" - a start at least...
Yeah, I knew about that possibility before, but since the data to be stored on Mozilla servers was being properly encrypted on my device and in my client, I opted out of the usual "maintain my own infrastructure" chores that one time. Now, the "old" (read: current) Firefox Sync system is going away completely in the not too distant future, and you'll probably have to install some kind of add-on to keep your existing, self-hosted infrastructure functional. Meanwhile, I asked some Mozilla people/developers what the change was about, and how the new system is supposed to keep users' data confidential. The transcript of the IRC session is available here, on Debian's inofficial pastebin - enjoy! :)
:%s/Open Source/Free Software/g
YTARY!
The browser could at least help, by not automatically assuming that everyone wants JavaScript support and re-enabling it even for anyone who willfully turned it off in the first place, while at the same time removing the GUI, requiring digging through the bowels of the hell that is about:config just to find the option to re-enable. The first step to cutting web bloat is to disable JavaScript, but ironically Mozilla seems to be directly against this idea.
The new server code/service building blocks are already (at least in part) available: https://github.com/mozilla/fxa... https://github.com/mozilla/fxa... - there's probably more, but mozila shares so much on github I don't really know what to look for.
:%s/Open Source/Free Software/g
YTARY!