Slashdot Mirror


Firefox 43 Arrives With 64-bit Version For Windows, Android Tab Audio Indicators (venturebeat.com)

An anonymous reader writes: Mozilla today launched Firefox 43 for Windows, Mac, Linux, and Android. Notable additions to the browser include a 64-bit version for Windows (finally!), a new strict blocklist for the browser's tracking protection feature, and tab audio indicators on Android. "There is, however, a bit of a caveat. Firefox 64-bit for Windows has limited support for plugins. Certain sites that require plugins and work in Firefox 32-bit might not work in this 64-bit version. But Mozilla doesn’t see this as a big problem, and says it is by design. After all, the company plans to drop support for NPAPI plugins in Firefox by the end of the year (though it will keep Flash around). Mozilla has just over two weeks to deliver on that promise." Here are the changelogs: desktop and Android.

36 of 188 comments (clear)

  1. By Design by rudy_wayne · · Score: 3, Insightful

    But Mozilla doesnâ(TM)t see this as a big problem, and says it is by design.

    Yes, the shittyness of Firefox is by design.

    1. Re:By Design by BitZtream · · Score: 4, Insightful

      Netscape has never been able to actually pay attention to what the users of its browser want. The new netscape, which you kids know as mozilla, is behaving 100% EXACTLY like the old Netscape ...

      Firefox stopped being the best browser right about the time ie6 was deprecated. Yes, IE sucks, but FF sucks more actually.

      This is all simply an extension of their inability to write a browser.

      Not that they don't have some talented developers, they do ... but they just let them do whatever they want and have no focus on actually delivering something users want, so they keep coming up with all these retarded silly side projects and all these retarded bloated 'features' in firefox ... its only taken them 15 years to realize doing everything in XPCOM and JavaScript was a fucking stupid idea.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    2. Re:By Design by bhcompy · · Score: 5, Insightful

      Unfortunately, it's the browser with the best implementation of NoScript. Thus, it is indispensable.

    3. Re:By Design by MightyYar · · Score: 4, Insightful

      For me it is "Tree Style Tabs". Unfortunately, Mozilla plans to phase out the current extension framework in favor of something more along the lines of what Chrome does - so we'll both be screwed shortly. But in the meantime, Firefox's killer feature is its extensions.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    4. Re:By Design by Darinbob · · Score: 5, Insightful

      What's wrong with acting exactly like how the older product worked? Newer is not better. A web browser is simple, it doesn't need biweekly changes to its UI. the old Netscape was just fine. Web browser as an application platform is the dumb idea. DRM in browsers is a dumb idea.

      If firefox goes away then there is literally nothing left. A browser must support adblock and noscript, as well as general purpose plugins.

    5. Re:By Design by Excelcia · · Score: 2

      Palemoon

    6. Re:By Design by nevermore94 · · Score: 2

      I think this removal of NPAPI is highly premature. Chrome removed it earlier this year leaving Firefox as the best non-IE choice for my needs. Our company relies on 2 different browser based products, one for our thousand employees remotdesktopping into our company and another for our employees remote VPN connecting into thousands of customer servers. Both of these products require NPAPI to function. So, I will either have to stay on an old version of Firefox or be forced to use IE until the providers of these products get their software updated.

      --
      Nevermore.
    7. Re:By Design by rudy_wayne · · Score: 4, Insightful

      Firefox suffers from the syndrome known as "Bikeshedding".

      They long ago abandoned what should be their core focus -- fix bugs, improve performance and implement new standards as needed (CSS 3, HTML 5) -- and have focused instead on endless tinkering, completely destroying the UI and a parade of useless new "features".

    8. Re:By Design by sfosparky · · Score: 3, Interesting

      I was not familiar with the term "bikeshedding". Now I am -- thanks for that. And I was delighted to learn the term in the context of Firefox's constant breaking of the browser's U.I. for no good reason. Thanks to the many of other commentors who have articulated in their own different ways what I too believe about Firefox's usability destroying "upgrades". When I first heard about another FF "upgrade", my first reaction was to wonder, what part of the user interface that didn't need changing was going to be destroyed this time?

    9. Re:By Design by Darinbob · · Score: 4, Insightful

      I'm all for fixing the security problems. Moving stuff around on the UI has nothing to do with security.

    10. Re:By Design by hairyfeet · · Score: 2

      Except as TFS points out they are killing the plug in framework thus making their transformation into a shitty ersatz Chrome complete.

      If you wish to keep your extensions I suggest you migrate to either Pale Moon or Comodo Icedragon as both of those have forked away and will be keeping the extension framework. The main difference is that Icedragon has the new style UI, Pale Moon has kept the original FF UI, so you can simply pick which UI suits you best and call it a day.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    11. Re:By Design by Barefoot+Monkey · · Score: 4, Informative

      NoScript is an extension, not a plugin. Those are two completely different kinds of addons. Mozilla's quite particular about that distinction.

      Extensions are the things we all know and love, like uBlock, NoScript, GreaseMonkey etc. Plugins are things like Flash, the Java web plugin for running applets, Google Update, Silverlight, and so on. For the most part we really don't need plugins.

    12. Re:By Design by Merk42 · · Score: 2

      What actually is wrong with Firefox then?

      It doesn't solve 100% of the uses cases for 100% of people, therefore it is shit. I, of course, know what makes the perfect browser, but will not do anything to make it happen lest I be shown to be unsuccessful.

    13. Re:By Design by MightyYar · · Score: 2

      That blog post keeps a little bit of hope alive, but honestly it also raises alarm bells. It's clear they are moving ahead with a strategy that they have not clearly thought out. The good news for us little folk is that they are doomed to fail with the current approach.

      Our big fear is that, once we provide a WebExtensions API, there won’t be anything to motivate people to switch over to it.

      They are right to be afraid, because without a clear answer to this, that is exactly what will happen.

      Kind of sad that they will spend so much time on a failed effort, but it's not my money and not my effort.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
  2. So... by Anonymous Coward · · Score: 5, Insightful

    Which about:config preferences do I have to mess with to disable all the unwanted "features" in this version?

    1. Re:So... by Anonymous Coward · · Score: 4, Informative

      Which about:config preferences do I have to mess with to disable all the unwanted "features" in this version?

      browser.urlbar.unifiedcomplete to false will remove the worthless "Search For..." entry from the autocomplete dropdown when typing in the URL bar.

    2. Re:So... by X0563511 · · Score: 2

      Start with "about:config?filter=browser.urlbar.unifiedcomplete" - also consider "about:config?filter=xpinstall.signatures.required" if you need to use unsigned addons.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    3. Re:So... by rsmith-mac · · Score: 4, Insightful

      browser.urlbar.unifiedcomplete to false will remove the worthless "Search For..." entry from the autocomplete dropdown when typing in the URL bar.

      Thank you! That was driving me insane.

  3. Re:Time to upgrade by ArchieBunker · · Score: 2, Interesting

    Chrome. Now before anyone mentions calling home to Google and spying on you, can anyone demonstrate this behavior? Surely by now someone has captured packets of what is being sent.

    --
    Only the State obtains its revenue by coercion. - Murray Rothbard
  4. Re:Time to upgrade by jlv · · Score: 4, Insightful

    I won't use Chrome again until there is a reliable way to prevent extensions from auto-updating. I got tired of finding out "surprise!" that something that worked yesterday is no longer around because the extension has gone "pay".

  5. Re:Time to upgrade by Darinbob · · Score: 5, Insightful

    Chrome has all the disadvantages of Firefox, but from Google. Rapid fire unnecessary updates unrelated to security, dropping of support for plugins, development oriented towards developers rather than users, frequent kissing of advertising butts, etc.

  6. Recently tried out the nightly builds v.45 64bit by AbRASiON · · Score: 4, Interesting

    So I'm a bit of a Firefox loony, maybe visible from my post history.

    I've been a "hardcore" web browser, ever since using NetCaptor (a shell replacement for Internet Explorer which offered tabbed browsing, IIRC the first tabbed browser)
    Anyhow, I like Chrome performance but GREATLY dislike my ability to customise it, specifically tab control (which tab will the app go to if I close the current tab, left or right? will a new tab open in the foreground? what if I middle click a URL, foreground / background?)

    I've loved FireFox for years, but the 32bit builds are frankly, unstable dog shit for me, crash extremely regularly.
    I switched maybe 12 to 18 months back to WaterFox, some dude compiling up the 64bit code of FireFox and packaging it. It runs exactly the same as FireFox for me, all plugins work and it virtually never crashes. Problem is, as an "extreme" browser (anywhere from 30 to 300 tabs open at a time) FireFox / WaterFox can get slow.
    REALLY slow, CTRL-TAB to change tab? Can take .5 to 3 seconds. Clicking some buttons can be slow to react. Generally after a few seconds of switching into a tab though, it responds /mostly/ ok (Don't even think about Flash Video in a tab though, I just put that into Chrome and drop it on to a second monitor)
    I just checked, I currently have 393 tabs open (working on getting this down) of all the things I'm currently reading / researching etc.

    So to get to the point,.....
    I was hoping that E10s (Electrolysis, multi-threaded Firefox) would fix my problems, when it finally got better. I installed said nightly builds and I have to report that sadly. The performance difference between WaterFox and standard 64bit FF Nightly 45 (with E10s) virtually identical to one and other.
    I've confirmed E10s is on and being a nerd but without programming skills, I kind of blindly, optimistically figured, hey, latest builds, 64bit official, e10s, I bet if anything nightly might be less stable but fast as hell!
    Not in the slightest, it really is virtually identical :/ the one surprising thing I'd say is it's stable as heck for me. I notice almost no different between WaterFox and Nightly 45.
    Note: I did try this, with and without my plugins to make FF nice and usable.

    For what it's worth, my #1 plugin I can't live without is Tab Mix Plus. That fine control on tab behaviour and the fact I'm an extensive keyboard shortcut guy, makes the browser far, far more usable for me. I'd say I browse between 4 to 12 hours a day, every day.

    Please note, I do COMPLETELY realise that running in excess of 30 to 50 tabs is ridiculous, but back 6 years ago, I could do this under FF32 and while it was unstable, the performance of the primary UI for FF was fine.
    All I want the damn code to do is HIGHLY prioritise the current tab in front of the user and HIGHLY prioritise the ability to switch tabs, preferably the ones nearby (left, right of the active tab) - the process of going between them shouldn't be slow. Considering I've got 4 threads at my disposal here, it's a bit of a shame.

    At least it's stable and at least I can control the behaviour and look, how I like. I think Googles stubborn attitude towards Chrome is ghastly, personally.

  7. Re:Time to upgrade by Anonymous Coward · · Score: 2, Insightful

    Every time you go to a google site (google, gmail, etc), it "calls home". And it leaves plenty of traces. Of course, it's not forcing people to do that. But it encourages.

    But yes, it also calls home by itself by insidiously installing google Keystone at the first opportunity.

  8. Firefox 43.... by Excelcia · · Score: 5, Insightful

    The version number almost says it all. How can you get excited about a new Firefox release with any feature, when it's just another rapid release. It could have true hard AI and no one would notice any more. It would get lost in the staggeringly mediocre array of non-features nobody wants, forced UI changes, broken addons, and developers that decide they know more about what people want than the users do.

    Firefox adopted Google's rapid release cycle on a project that it was neither technically nor culturally suited for. One has to actually admire their dogged persistence to holding course in the face of what is an almost a completely unified chorus of "WHAT THE FUCK PEOPLE?!?!?".

    I recommend Palemoon. A fork of the previous Firefox LTR, it has refused to add features unless they make sense, is compatible with most addons, and has its own growing body of its own addon developers that are quite loyal to the project for the simple reason that the project remains loyal to them. That's not to say that it's a static browser. Just one that took the best of what Firefox was and decided to continue in the direction of sensible goals and not alienating its user base.

  9. Re:Time to upgrade by BrookHarty · · Score: 2

    Chrome was severely broken from the Dec 2nd to the 8th due to the 48.x upgrade, NTLM didnt work with squid based proxy servers. It broke offices around the world for a week, since chrome auto updates. And if you're a google office user, it impacted your entire company.

    Google knew about this issue in regression, fixed it, yet it still made it into production code due to the "devops" mentality..
    https://code.google.com/p/chro...

    A major problem with firefox, it doesnt support installed certificates in windows. Chrome does. We use certificates tied to the users PC/VM with google office, so users cant log into google email except from their 1 verified instance. (and tied to their mobile iron on the apple/android phone)....

    I WANT to use Firefox, but I'm tied to Chrome if I want to read my mail. (we have pop/imap/apps turned off too, since we don't have password access, sigh, i miss thunderbird...)

    And this monday, keepass stopped working with my chrome and firefox on my linux box, and firefox uses keefox, chrome uses chromelpass..

    JAVA! I still use it for dell idracs, but I cant use chrome to access idracs now. And Firefox with its dell signed ssl cert issues, sigh, always deleteing them after adding them so they dont conflict.

    I'm not happy with browsers in general, continuously breaking, non compatible apps..

  10. Re:Time to upgrade by labnet · · Score: 2

    Does chrome support tree tabs as well as the firefox treetabs extension. (I dropped chrome because I could find no such functionality)
    I don't know how people browse without vertical tabs (I usually have 60+ tabs open at a time)

    --
    46137
  11. Hooray! by Etherwalk · · Score: 5, Funny

    Same problem every other 64bit browser has that uses plugin made under designs from 20 years ago

    But with 64 bits, Firefox will finally be able to address all the memory it uses!

  12. It's 64 bit now? by AndyKron · · Score: 2

    It's 64 bit now? Woo Hoo! I can wait faster!

    1. Re:It's 64 bit now? by alantus · · Score: 2

      It's been 64 bit for almost six years.

      $ file /usr/lib/firefox/firefox

      /usr/lib/firefox/firefox: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs)

      Strange, I get a different output:

      C:\>file /usr/lib/firefox/firefox
      'file' is not recognized as an internal or external command,
      operable program or batch file.

  13. Re:Time to upgrade by rudy_wayne · · Score: 2

    Chome's UI is shit and can't be changed. One of the best features of Firefox has always been the ability to rearrange things exactly how I want, instead of being forced to use what someone else dictates. Of course Firefox eliminated much that a while back in their quest to be more like Chrome.

  14. Can't upgrade by DeHackEd · · Score: 2

    Remember back when IE 6 refused to die because corporations had ActiveX stuff that prevented upgrading? NPAPI has become like that as well. I can't upgrade because I have apps that run as Java applets and I'll lose them. I already can't use Chrome...

    So, here's to vendors migrating away from Java and issuing updates I guess...

    (And I find it ironic that Flash gets some kind of exception even though even Adobe wants it dead.)

  15. Why the instability in Firefox? FF dies? Pale Moon by Futurepower(R) · · Score: 2, Informative

    To me, the most important feature of Firefox is the add-ons. I like Session Manager, for example.

    Question about Firefox: Microsoft's Process Explorer shows that Firefox uses the CPU while no Firefox windows are in the foreground. Why? Firefox's CPU use is especially intense when many windows and tabs are open. Also Process Explorer shows that often Firefox continually adds memory to its "Private Bytes" and "Working Set", even when there is no Again, why?

    Someone above mentioned Pale Moon. Pale Moon has a 64-bit edition.

    Joke:
    Instead of browser.pocket.enabled = false in Firefox, try:
    browser.adult.supervision.enabled = true in Pale Moon. (Not a real Pale Moon choice, of course.)

    Pale Moon has tools for backup and migration. Adblock Latitude blocks ads. There are other Pale Moon ad-ons, and usually Firefox add-ons work perfectly.

    "Pale Moon Commander ... provides a user-friendly interface to advanced preferences that would otherwise require manual editing of parameters, which can be cumbersome and time-consuming to do."

  16. Re:Recently tried out the nightly builds v.45 64bi by Anonymous Coward · · Score: 3, Interesting

    No, a browser not being able to handle 50 tabs is ridiculous. That's like a document editor that fails after 100 pages (or all the text editors that crap out when you have 0.5MB of text on a single line). I use Firefox with under 2500 tabs. Anything over 1500 and Firefox starts crapping all over itself, but I've been up to around 2500 before (most of these are suspended tabs, though they seem to take up far more resources than they should. Suspended tabs should be the equivalent of bookmarks but they aren't.) I search for something or go to a site like Slashdot and open up every link or article I'd like to read as new tabs. Then I go through each tab closing as I finish. Many pages have more interesting links, so the tabs tend to grow faster than I consume them. I could use bookmarks, but I really like the contextual info tabs give you. I can scroll through my tab bar and remember what I was thinking about when dealing with tabs from that time. They show the thought pattern I had at the time and make it easier to pick up where I left off. Bookmarks don't give you that. Bookmarks force you to try to organize them in some way. My tabs are self organizing.

    Using so many tabs really brings out some horrible design decisions Firefox has. GIFs and animations keep playing in other tabs. They shouldn't. There's no reason for the stupid flashing background to keep flashing when you're not looking at it but it does. The animated download arrow is super annoying. The entire browser freezes when that thing plays and the animation freezes while whatever was downloaded gets saved to disk. Why it takes 2-5 seconds to save a 1MB image I have no idea, but that's how long it takes the browser to process it even when the webpage (which has the image and a bunch of other content) loaded faster than that. Clearing the download history reduces the frozen time... WTF is up with that? Adding something to a download database should be a constant time operation no matter how big the database is. What's going on under the hood?

  17. Re:can someone explain why it lagged so much on Wi by OhPlz · · Score: 2

    I remember using Minefield at least as far back at 2010, a bit earlier I think. So it was there for Windows, it just wasn't a fully legit release that you could get from the normal download page. It worked fine for nearly everything including plugins, although as mentioned Flash was a problem if you cared about Flash. I jumped over to Palemoon when the CEO thing happened at Mozilla, it had 64 bit as a regular download. Why it took Firefox so long.. hey, they have a lot of useless features to add and useful features to remove. It takes time!

  18. Re:Time to upgrade by rsborg · · Score: 3, Funny

    Chrome has all the disadvantages of Firefox

    Really? Because video on Firefox sucks ass, but on Chrome it's slicker than snot.

    What are you running, a Dual-Pentium?

    --
    Make sure everyone's vote counts: Verified Voting
  19. Lightning Fast by nowsharing · · Score: 3, Informative

    I just moved to the 64-bit FF and it's lightning fast and my entire big list of extensions still work perfectly. I'm really impressed. My only gripe is that the about:config hack to restore the old drop-down search engine list isn't working yet. The string is still there though, so I assume it will come back to life eventually.