Welcome to nsane.forums

Welcome to nsane.forums, like most online communities you need to register to view parts of our community or to make contributions, but don't worry: this is a free and simple process that requires minimal information. Be a part of nsane.forums by signing in or creating an account.

  • Access special members only forums
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates

Search the Community

Showing results for tags 'firefox'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Found 561 results

  1. Netflix now runs on Linux with Mozilla Firefox It took them a few years to realize that Linux could be a very important player for their video-on-demand streaming platform, and now Netflix is announcing that it "finally" supports playback on the Mozilla Firefox web browser. Numerous Linux users are using Mozilla Firefox on their computers because it's usually the default web browser shipped with the GNU/Linux distribution of their choice. Of course, many others also use Google Chrome or Chromium, or something else that's based on the latter, such as Opera or Vivaldi. Until today, if you wanted to watch Netflix movies and TV shows on your Linux computer, you would have to install Chrome or a Chrome-based web browser. But not anymore, because Netflix just made it possible for the rest of the Linux users using Mozilla Firefox to enjoy their content. "And though we do not officially support Linux, Chrome playback has worked on that platform since late 2014. Starting today, users of Firefox can also enjoy Netflix on Linux," reads the announcement. "This marks a huge milestone for us and our partners, including Google, Microsoft, Apple, and Mozilla that helped make it possible." How to watch Netflix content with Mozilla Firefox No, it's not a tutorial because there's no need for one anymore. We only to inform you that if you want to watch Netflix movies and TV shows using Mozilla Firefox, all you have to do is to make sure you have the latest version installed. According to Netflix, Mozilla Firefox 47 or later is required for their DRM content to work on HTML5. However, it would appear that both Mozilla Firefox and Google Chrome only support video playback up to 720p resolution. The company says that this is only the beginning, as they plan high-resolution video playback on more platforms soon. 1080p and 4K content can only be watched using Microsoft Edge, Internet Explorer or Safari, the latter two only offering up to 1080p playback. Source
  2. Mozilla Fixes Critical Vulnerability in Firefox 22 Hours After Discovery White hats were rewarded $30,000 for the effort The new Firefox version 52.0.1 which was released late on Friday contains the patch for the flaw discovered by hackers in the competition. The fix was confirmed via Twitter by Asa Dotzler, Mozilla participation director for Firefox OS, as well as Daniel Veditz, security team member at Mozilla. The bug was discovered by the Chaitin Security Research Lab from China. The hackers managed to escalate privileges in an exploit during the hacking competition by combining the bug with an initialized buffer in the Windows kernel. The bug bounty for this particular vulnerability was of $30,000 indicating that it was a serious matter. In a security advisory published by Mozilla, the company marks the integer overflow in the createImageBitmap() as "critical." They say that the bug was fixed in the newest version by disabling experimental extensions to the createImageBitmap API. Mozilla also claims that since the function works int he content sandbox, it would have required a second vulnerability to compromise a user's computer. Chaitin used, in this instance, the Windows kernel. Largest awards so far Many vulnerabilities were discovered during the hacking competition. So far, few have been fixed, and definitely not many as fast as the one Mozilla patched up in Firefox. Microsoft and Apple are two of the companies people are waiting to hear from int his regard In total, contestants were awarded $833,000 for the discovered vulnerabilities this year, nearly double than what was awarded last year. In 2016, the awards reached $460,000 and the previous year $577,000. In the end, it all depends on how good a day the hackers have to find something critical to exploit. Source
  3. Firefox warns users about unencrypted pages We suppose it was only a matter of time before someone had a complaint about the notifications browsers display when a website accepts logins over unencrypted HTTP pages. In fact, Mozilla has received a complaint about this very "issue." Folks over at Ars Technica spotted the complaint over on Mozilla's Bugzilla bug-reporting service. "Your notice of insecure password and/or log-on automatically appearing on the log-in for my website, Oil and Gas International, is not wanted and was put there without our permission. Please remove it immediately. we have our own security system, and it has never been breached in more than 15 years. Your notice is causing concern by our subscribers and is detrimental to our business," the message signed by dgeorge reads. Of course, they seem to be late to the party since this type of warnings have been showing for a few months now and became standard earlier this year for both Firefox and Chrome. The benefits of HTTPS Thankfully, someone from Mozilla came forward and cleared things up for dear ol' dgeorge telling him that when a site requests a user's password over HTTP, the transmission is done in the clear. "As such, anybody listening on the network would be able to record those passwords. This puts not just users at risk when using your site, but also puts them at risk on any other website that they might share a password with yours," they explain. In the end, it's been proven time and time again, that providing email and passwords over HTTP is no longer safe. For years now, there's been a push for HTTPS and web admins have been given plenty of time to make the change, both for their sake and their users' sake. Now, Chrome will display a "Not Secure" notification next to the address bar, while Firefox takes things a step further, displaying below the user name and password fields "this connection is not secure. Logins entered here could be compromised." Source
  4. If you are a Firefox user and pay attention to user reviews and ratings on the Firefox add-ons website, you may have noticed an increase in anonymous ratings. The ratings are left by anonymous user "random six character string", and only have a rating but no review itself. This in itself is strange for veteran Firefox users, considering that one of the requirements for leaving reviews was leaving a comment up until now. One example where you can see the new influx of reviews is the Adblock Plus reviews page on Mozilla AMO. Anonymous Firefox add-on ratings As you can see on the screenshot above, the first three ratings have been left by anonymous users. You can click on the username to find out more about that user. No matter how many you check, you will notice that they have all been created on the same day the rating was left. So where are those anonymous user accounts coming from? Webmasters may have seen similar activities by anonymous and random users leaving comments on sites, and one fear that users and add-on authors may have that this is a spam campaign. The first thing that comes to mind is spam, probably because of that. This is not the case however. According to this discussion on Mozilla's official Add-ons forum, anonymous ratings come from users who run Firefox mobile. This is because the new mobile site was recently launched. You can test it yourself by visiting AMO on a mobile device, or scrolling to the bottom of the page and clicking on "View Mobile Site". You'll notice the new rating UI lets you submit a star rating without a written review. This is intentional. We think this will encourage more people to rate add-ons, and will reduce the instances of written reviews that don't say much or end up being deleted because of the way they're worded. This is confirmed on the Mozilla Addons Server Github page. It confirms that blank reviews will come to the desktop site as well. We're supporting blank reviews now. The recent ones come from the mobile site, which is the first one to support this. The desktop site will support it in the future as well. Firefox users on mobile devices still need a Firefox account to leave reviews, but the requirement for leaving a comment / explanation has been removed by Mozilla. It is unclear why Mozilla's site shows these ratings as anonymous, as opposed to listing the Firefox account username. One explanation may be that you only need to set an email address and password during registration, so that there is no username for a particular user at that point in time. As far as I see it, there are two issues with these reviews. First, that they look like spam, and second, that they don't add any value besides adding a rating. Mozilla's main idea behind lifting the requirement to leave a comment when rating an add-on is that it does away with meaningless reviews by users who did not want to write anything but still rate an add-on. The fact that these are now replaced by empty reviews that clutter the review listing refutes that argument. It would be easy enough to solve part of the issue right away though, as Mozilla would only have to find a way to remove empty reviews from the reviews listing. Article source
  5. Mozilla Firefox 53.0 Beta 3 Firefox is the award winning next generation browser from Mozilla. Firefox empowers you to browse faster, more safely, and more efficiently than with any other browser. Make the switch today - Firefox imports your Favorites, settings and other information, so you have nothing to lose. Stop annoying popup ads in their tracks with Firefox's built in popup blocker. View more than one web page in a single window with this time saving feature. Open links in the background so that they're ready for viewing when you're ready to read them. Built with your security in mind, Firefox keeps your computer safe from malicious spyware by not loading harmful ActiveX controls. A comprehensive set of privacy tools keep your online activity your business. Homepage Changelog Download | 32-bit | Download | 64-bit - Windows en-US Download | 32-bit | Download | 64-bit - Windows All Languages Download - Other OS Download - Android Official Download Page-Beta: https://www.mozilla.org/en-US/firefox/beta/all/ Checksum: SHA512SUMS SHA512SUMS.asc Beta candidates(build 1): https://download-installer.cdn.mozilla.net/pub/firefox/candidates/53.0b3-candidates/build1/ Android beta candidates(build 1): https://download-installer.cdn.mozilla.net/pub/mobile/candidates/53.0b3-candidates/build1/
  6. Mozilla Firefox 52.0.1 RC 2 Windows en-US: x86: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1-candidates/build2/win32/en-US/Firefox%20Setup%2052.0.1.exe x64: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1-candidates/build2/win64/en-US/Firefox%20Setup%2052.0.1.exe Windows All languages: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1-candidates/build2/win32/ https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1-candidates/build2/win64/ Other OS: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1-candidates/build2/ Checksum: SHA512SUMS SHA512SUMS.asc Firefox for Android 52.0.1 RC: https://download-installer.cdn.mozilla.net/pub/mobile/candidates/52.0.1-candidates/
  7. Mozilla Firefox 52.0.1 ESR RC 1 Note: Only Linux candidates RC downloads available for Build 1. Use Build 2 for Windows & Mac[Other OS] posted below. Windows en-US: - Not Available for this RC 1. Use RC 2 below. x86: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1esr-candidates/build1/win32/en-US/Firefox%20Setup%2052.0.1esr.exe x64: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1esr-candidates/build1/win64/en-US/Firefox%20Setup%2052.0.1esr.exe Windows All languages: - Not Available for this RC 1. Use RC 2 below. https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1esr-candidates/build1/win32/ https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1esr-candidates/build1/win64/ Other OS: - Available - Linux Only https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1esr-candidates/build1/ Checksum: SHA512SUMS - Not Available for this RC 1. Use RC 2 below. SHA512SUMS.asc - Not Available for this RC 1. Use RC 2 below. Mozilla Firefox 52.0.1 ESR RC 2 Windows en-US: x86: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1esr-candidates/build2/win32/en-US/Firefox%20Setup%2052.0.1esr.exe x64: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1esr-candidates/build2/win64/en-US/Firefox%20Setup%2052.0.1esr.exe Windows All languages: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1esr-candidates/build2/win32/ https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1esr-candidates/build2/win64/ Other OS: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0.1esr-candidates/build1/ Checksum: SHA512SUMS SHA512SUMS.asc @coua & @Kalju: I think you both didn't notice the Notes above links. I've clearly stated that only Linux version is available for this build 1 at the time of posting. @coua: You can check your quote too. Now, build 2 is released and it is available for all OS.
  8. WebAssembly, a new binary execution format for the Web, is starting to arrive in stable versions of browsers. A major goal of WebAssembly is to be fast. This post gives some technical details about how it achieves that. Of course, “fast” is relative. Compared to JavaScript and other dynamic languages, WebAssembly is fast because it is statically typed and simple to optimize. But WebAssembly is also intended to be as fast as native code. asm.js has already come quite close to that, and WebAssembly narrows the gap further. This post focuses therefore on why WebAssembly is faster than asm.js. Before we start, the usual caveats: Performance is tricky to measure, and has many aspects. Also, in a new technology there are always going to be not-yet-optimized cases. So not every single benchmark will be fast on WebAssembly today. This post describes why WebAssembly should be fast; where it isn’t yet, those are bugs we need to fix. With that out of the way, here is why WebAssembly is fast: 1. Startup WebAssembly is designed to be small to download and fast to parse, so that even large applications start up quickly. It’s actually not that easy to improve on the download size of gzipped minified JavaScript, as it’s already fairly compact when compared with native code. Still, WebAssembly’s binary format can improve on that, by being carefully designed for size in mind (indexes are LEB128s, etc.). It is often around 10–20% smaller (comparing gzipped sizes). WebAssembly improves on parsing in a much bigger way: It can be parsed an order of magnitude faster than JavaScript. This mostly comes down to binary formats being faster to parse, especially ones designed for that. WebAssembly also makes it easy to parse (and optimize) functions in parallel, which helps a lot on multicore machines. Total startup time can include factors other than downloading and parsing, such as the VM fully optimizing the code, or downloading additional data files that are necessary before execution, etc. But downloading and parsing are unavoidable and therefore important to improve upon as much as possible. All the rest can be optimized or mitigated, either in the browser or in the app (for example, fully optimizing the code can be avoided by using a baseline compiler or interpreter for WebAssembly, for the first few frames). 2. CPU features One trick that’s made asm.js so fast is that while all JavaScript numbers are doubles, in asm.js an addition will have a bitwise-and operation right after it, which makes it logically equivalent to the CPU doing a simple integer addition, which CPUs are very good at. So asm.js made it easy for VMs to use a lot of the full power of CPUs. But asm.js was limited to things that are expressible in JavaScript. WebAssembly isn’t limited in that way, and lets us use even more CPU features, such as: 64-bit integers. Operations on them can be up to 4x faster. This can speed up hashing and encryption algorithms, for example. Load and store offsets. This helps very broadly, basically anything that uses memory objects with fields at fixed offsets (C structs, etc.). Unaligned loads and stores, avoiding asm.js’s need to mask (which asm.js did for Typed Array compatibility purposes). This helps with practically every load and store. Various CPU instructions like popcount, copysign, etc. Each of these can help in specific circumstances (e.g. popcount can help in cryptanalysis). How much a specific benchmark benefits will depend on whether it uses the features mentioned above. We often see a 5% speedup on average compared to asm.js. Further speedups are expected in the future from CPU features like SIMD. 3. Toolchain Improvements WebAssembly is primarily a compiler target, and therefore has two parts: Compilers that generate it (the toolchain side), and VMs that run it (the browser side). Good performance depends on both. This was already the case with asm.js, and Emscripten did a bunch of toolchain optimizations, running LLVM’s optimizer and also Emscripten’s asm.js optimizer. For WebAssembly, we built on top of that, but have also added some significant improvements while doing so. Both asm.js and WebAssembly are not typical compiler targets, and in similar ways, so lessons learned during the asm.js days helped do things better for WebAssembly. In particular: We replaced the Emscripten asm.js optimizer with the Binaryen WebAssembly optimizer, which is designed for speed. That speed lets us run more costly optimization passes. For example, we remove duplicate functions by default when optimizing, which often shrinks large compiled C++ codebases by around 5%. Better optimizations for irreducible and convoluted control flow, improving the Relooper algorithm. Helps a lot on compiled interpreter-type loops. The Binaryen optimizer was designed with experimentation in mind, and experiments with superoptimization have led to miscellaneous minor improvements — things which could have been done in asm.js too, had we thought of them. Overall, these toolchain improvements help about as much as moving from asm.js to WebAssembly helps us (7% and 5% on Box2D, respectively). 4. Predictably Good Performance asm.js could run at basically native speed, but it never actually did so in all browsers consistently. The reason is that some tried to optimize it one way, some another, with differing results. Over time things started to converge, but the basic problem was that asm.js was not an actual standard: It was an informal spec of a subset of JavaScript, written by one vendor, that only gradually saw interest and adoption from the others. WebAssembly, on the other hand, has been designed jointly by all major browsers. Unlike JavaScript, which could be made fast only using very creative methods, or asm.js, which could be made fast using simple methods but not all browsers did so, WebAssembly has more agreement upon how to optimize it. There is still plenty of room for differentiation in VMs (different ways to tier compilation, AOT vs. JIT, etc.), but a good baseline of predictable performance can be expected across the entire Web. Article source
  9. Mozilla Firefox 53.0 Beta 2 Firefox is the award winning next generation browser from Mozilla. Firefox empowers you to browse faster, more safely, and more efficiently than with any other browser. Make the switch today - Firefox imports your Favorites, settings and other information, so you have nothing to lose. Stop annoying popup ads in their tracks with Firefox's built in popup blocker. View more than one web page in a single window with this time saving feature. Open links in the background so that they're ready for viewing when you're ready to read them. Built with your security in mind, Firefox keeps your computer safe from malicious spyware by not loading harmful ActiveX controls. A comprehensive set of privacy tools keep your online activity your business. Homepage Changelog Download | 32-bit | Download | 64-bit - Windows en-US Download | 32-bit | Download | 64-bit - Windows All Languages Download - Other OS Download - Android Official Download Page-Beta: https://www.mozilla.org/en-US/firefox/beta/all/ Checksum: SHA512SUMS SHA512SUMS.asc Beta candidates(build 1): https://download-installer.cdn.mozilla.net/pub/firefox/candidates/53.0b2-candidates/build1/ Android beta candidates(build 1): https://download-installer.cdn.mozilla.net/pub/mobile/candidates/53.0b2-candidates/build1/
  10. Top Firefox Add-ons, And Their WebExtensions Status The following article looks at a list of top Firefox add-ons, and checks whether those add-ons are available as WebExtensions already, or are planned to be released as WebExtensions. Top Firefox add-ons in this context means the following: first page of add-ons on Mozilla AMO based on user count, user rating, and featured. Mozilla plans to drop legacy add-on support with the release of Firefox 57. While legacy add-ons will live on for a while in Firefox ESR and development builds of the browser, these exceptions will be removed eventually as well. Considering that Firefox 57 will be released in November 2017, it is important to look at the current state of add-on migration. Note: we did not list video downloaders. Note: The availability as a WebExtension does not necessarily mean that you will get the same functionality or layout. Also note that a status of unknown does not mean that a WebExtension is not in the works. It simply means that I was not able to find information about it online. Firefox Add-ons with the Most Users Adblock Plus -- WebExtension is being worked on. See Bug uBlock Origin -- WebExtension is being worked on. See GitHub page. Easy Screenshot -- Unknown.. NoScript Security Suite -- WebExtension is being worked on. See our article. Firebug -- Will be integrated into Firefox natively. Search and New Tab by Yahoo -- Unknown. Ghostery -- Already available as WebExtension. DownThemAll -- Not going to happen. Greasemonkey -- Unclear, design document exists, but APIs missing. Mozilla tracking bug. iMacros for Firefox -- Unknown Google Translator for Firefox -- Unknown LastPass Password Manager -- LastPass 4.0 is a WebExtension. Tracking Bug. Tab Mix Plus -- Unknown, tracking bugs exist. FlashGot Mass Downloader -- Unknown. Developed by NoScript developer. YouTube High Definition -- Unknown. Top-Rated Firefox Add-ons Beyond Australis -- Not going to happen. Classic Theme Restorer -- Not going to happen. YouTube High Definition -- Unknown. OmniSidebar -- Not going to happen. Disable CTRL-Q Shortcut -- Unlikely, last update in 2012. YouTube Flash Video Player -- Unknown. Puzzle Bars -- Not going to happen. TableTools2 - Copy/Sort/Chart/Filter Table&More -- Unknown. Google search link fix -- Already a WebExtension. Theme Font & size Changer -- Unknown. Decentraleyes -- WebExtension is being worked on. Source. Add-ons Manager Context Menu -- Unlikely, last update in 2013. YouTube Plus -- Already a WebExtension. Magic Actions for YouTube -- Already a WebExtension. Classic Toolbar Buttons -- Not going to happen. Pray Times -- Unlikely, last updated in 2013. Pearltrees -- Unknown. Reader -- Unknown. Adblock Plus -- Being worked on. QuickMark -- Unknown. Top Featured Firefox Add-ons History Submenus II -- Unknown. Gmail Notifier+ -- Unknown. Copy Plain Text 2 -- Unknown. Clear Console -- Unknown. Dictionary (Google Translate) Anywhere -- Unknown. Tile Tabs -- Tile Tabs WE is a WebExtension version. Tab Scope -- Unknown. Private Tabs -- Unknown. Weather Forecast Plus -- Unknown. Lightbeam for Firefox -- In development. NoScript Security Suite -- Being worked on. Gmail Notifier (restartless) -- Unknown. Messenger & Notifier for Facebook -- Unknown. Enhancer for Youtube -- Seems likely, as a Chrome version exists. Torrent Tornado -- Unknown. BetterPrivacy-signed -- Unknown. Forecastfox (fix version) -- Seems likely, as a Chrome extension exists. Emoji Keyboard -- Unknown. Clean Uninstall -- Unknown. Cleanest Addon Manager -- Unknown. Stats Working: 6 Being Worked On: 5 Unknown: 33 Won't be available: 6 Closing Words We will revisit this page regularly to update the state of all listed browser add-ons for Firefox. Source
  11. Mozilla plans to make a change to Geolocation in Firefox 55 that would block requests automatically if they come from non-secure origins. Geolocation, broken down to its core, refers to technologies that allow sites and applications to determine a user's position in the world. This can be useful when mapping services are used among other things (show me where I'm, auto-filling of the current location). Many sites, not only mapping services but also shopping sites, or multi-lingual sites, use Geolocation for functionality. It is fairly common for instance that users are redirected automatically to a local version of the site if it exists. Firefox 55: Geolocation requires secure origin Mozilla plans to make the change in Firefox 55. The implementation is on the heels of the Chromium team which added the requirement to Chromium 50. Firefox 55 is scheduled for an August 2017 release. Basically, what this means for Firefox users is that Geolocation requests won't work anymore if a site or application does not use HTTPS. To be precise, Geolocation will also work in the context of encrypted WebSocket connections (wss://), and requests from local resources such as localhost. Mozilla notes that services that use non-secure origins for Geolocation requests will break when the change happens. Telemetry data that has been analyzed five months ago suggests that this will affect about 0.188% of page loads in the browser. Just looking at non-secure origin Geolocation requests, Telemetry data suggested that 57% of getCurrentPosition() requests and 2.48% of watchPosition() requests use non-secure origins. The figure will go down further in the future as more and more sites start the migration to HTTPS. If you run Firefox Nightly currently, which is at version 55 at the time of writing, you will notice that non-secure Geolocation requests still work. The feature is hidden behind a preference right now which you need to set to false to test right away: Type about:config in the browser's address bar and hit the Enter-key. Confirm that you will be careful. Search for geo.security.allowinsecure. Double-click on the preference to toggle it. Once you have set the preference to false, any Geolocation request from an insecure origin will fail. (via Sören) Article source
  12. Mozilla Firefox with its multi-process architecture enabled is still the web browser with the best memory performance according to Mozilla. Our own memory benchmarks saw Firefox lead the pack in 2012 and 2014 when we compared the browser's memory usage against Chrome, Opera and Internet Explorer on Windows. Mozilla did run tests of its own last year, and ran them again this year with multi-process versions of the browser. Multi-process architecture separates the browser from content processes in Firefox. Mozilla estimated last year that Firefox would use about 20% more memory with a single content process added, and more if more processes were used by the browser. The new test conducted by Mozilla takes different content process configurations into account. More precisely, Mozilla ran the same test that it did last year with 2, 4 and 8 content processes. Mozilla's loaded 30 web pages of the Alexa top 100 in their own tabs, with 10 seconds in between loads, and looked at the memory usage of the browser in the end. Firefox, Chrome, IE, Safari memory performance in 2017 The result, as you can see on the graph above is that Firefox is very memory efficient. This is particularly the case on Windows and Linux, where the memory use difference is significant. Firefox uses more memory if more content processes are added, but the difference between 2 and 8 content processes is not as problematic as Mozilla assumed last year. On Windows 10, memory performance increased by about 300 Megabyte from 587 MB to 905 MB with eight content processes enabled. On Linux, memory usage rose by just 125 Megabyte under the same eight content processes. The difference is not as spectacular on Mac devices. Firefox with two and four content processes uses less memory than Chrome, but the difference is just 150 Megabyte at the most. The eight content process version used even more memory than Chrome on the operating system. Chrome used 1478 MB on Linux, 1382 MB on Windows, and 1365 MB on Mac OS X. Mozilla's plan is to increase the number of content processes to four in the near future. This would make Firefox use less memory than Chrome on all platforms. On two, Windows and Linux, it would use considerably less than Chrome. It needs to be noted that Google Chrome uses one content process per tab by default. Firefox's memory usage would increase more if Mozilla would enable this as well. Tip: you can tame Chrome's memory usage by enabling processes per site, and not tab. This works for other Chromium-based browsers as well including Vivaldi and Opera. If you use Firefox, check out our guide on optimizing Firefox's memory use. Closing Words You can run the tests by yourself, as the tools that Mozilla used to run the benchmarks are openly available. It appears at least, that Firefox is still the most memory friendly user in 2017, and that the switch to the multi-process architecture has not changed that. While memory use increased, it is still better than Chrome, IE or Safari even with multiple content processes enabled. Article source
  13. The Classic Theme Restorer add-on for Firefox will stop working when Mozilla releases Firefox 57.0 Stable, and Firefox 59.0 ESR. Classic Theme Restorer was developed as a direct response to Mozilla refreshing Firefox with the Australis theme release in Firefox 29. The add-on allows Firefox users to restore many theme features that Mozilla removed and changed with the Australis launch, or introduced with it. The extension grew quickly, and features an immense set of features and tweaks nowadays that give you control over many features of the browser. Check out 10 reasons for Classic Theme Restorer to find out more about the add-on's functionality. The death of Classic Theme Restorer for Firefox Back in November 2016, we suggested that Classic Theme Restorer might be dead once Mozilla makes the full switch to WebExtensions exclusively in Firefox. We based this on posts by Aris, the developer of the add-on who stated that the extension will be dead by the end of 2017. Reasons given at that time were that Mozilla had not come up with WebExtension APIs that would allow the add-on to be ported, and then continued as a WebExtension. If you check out the official add-on page of Classic Theme Restorer on Mozilla's AMO site today, you will notice the following paragraph at the top: This add-on will stop working when Firefox 57 arrives in November 2017 and Mozilla drops support for XUL / XPCOM / legacy add-ons. It should still work on Firefox 52 ESR until ESR moves to Firefox 59 ESR in 2018 (~Q2). There is no "please port it" or "please add support for it" this time, because the entire add-on eco system changes and the technology behind this kind of add-on gets dropped without replacement. Aris posted a request on Bugzilla to get Mozilla to introduce APIs that would allow him to port the add-on, but Mozilla marked the request as Wontfix. This means basically, that Mozilla won't create the APIs required to port Classic Theme Restorer, and many of the other add-ons that require this kind of access. While the new theme API may introduce some features, it is too limited to create a viable WebExtension version of Classic Theme Restorer. Classic Theme Restorer, at the time of writing, is one of the highest rated add-ons on AMO. It has a five star rating based on 1176 user reviews, and more than 413,000 users at the time of writing. 413,000 users may not be much when compared to Firefox's total population. Most of these users have -- likely -- used Firefox for years, even before the Australis days. There is not much Firefox users can do about it if they rely on add-ons that cannot or won't be ported to WebExtensions. Sticking with the last working build may work for a time, but it means that security issues will pile up, and that support for new web technologies won't find its way into the browser either. Switching to third-party ports may be an option, but it remains to be seen how many of those will survive the year 2017. The developer of Cyberfox stated recently for instance that the browser will reach end of life with the release of Firefox 52.x ESR. Pale Moon will survive, but that is the only web browser based on Firefox that we know of that will do so. Article source
  14. Back in January, we told you that the development of the Mozilla Firefox 52.0 kicked off with the first Beta release and promised to let users send and open tabs from one device to another, among numerous other improvements and new features. Nine Beta builds later, Mozilla has pushed today, March 7, 2016, the final binary and source packages of the Mozilla Firefox 52.0 web browser for all supported platforms, including GNU/Linux, macOS, and Windows. The good news is that Firefox 52 is an ESR (Extended Support Release) branch that will be supported until March-April 2018. There are now two ESR branches available, namely Mozilla Firefox 52.0 and 45.x. The latter was updated today as well, to version 45.8.0, and will get one more security update, versioned 45.9.0, next month, when the new 52.0 series will receive its first point release, versioned 52.1, giving system integrators enough time to move to Firefox 52 ESR. What's new in Firefox 52.0 ESR Prominent features of the Mozilla Firefox 52.0 ESR release include support for the emerging WebAssembly standard to boost the performance of Web-based games and apps without relying on plugins, the ability to send and open tabs from one device to another, as well as multi-process for Windows users with touchscreens. With each new Firefox release, Mozilla's developers attempt to offer new way to improve the security of the widely-used web browser across all supported platforms. Firefox 52.0 ESR implements a "This connection is not secure" warning for non-secure pages that require user logins, along with a new Strict Secure Cookies specification. "Implemented the Strict Secure Cookies specification which forbids insecure HTTP sites from setting cookies with the "secure" attribute. In some cases, this will prevent an insecure site from setting a cookie with the same name as an existing "secure" cookie from the same base domain," explain the Mozilla developers in the release notes. Firefox 52.0 also improves the downloads experience by adding notifications for failed downloads, bigger buttons for restarting or canceling a download, and access to up to five of the most recent downloaded files. Other than that, it improves the text input for third-party keyboard layouts on Windows OSes. Additionally, it removes support for NPAPI (Netscape Plugin API) plugins except for Adobe Flash Player, which means that Microsoft's Silverlight, Oracle's Java or Adobe's Acrobat plugins are no longer supported. Mozilla Firefox 52.0 also removes the Battery Status API reducing browser fingerprinting by various trackers. For developers, Firefox 52.0 improves security for screen sharing, which no longer requires a whitelisted domain and displays a preview, enables CSS Grid Layout, and redesigns the Responsive Design Mode with network throttling, device selection, and other goodies. Download Firefox 52.0 for GNU/Linux, macOS, and Microsoft Windows. Article source Firefox 52.0 released: find out what is new
  15. Mozilla is working on an updated version of the preferences in the Firefox web browser to remove inconsistencies and improve the user experience. The Firefox preferences page allows users to modify various important browser settings such as the homepage, update behavior, or search engines. The page has not changed all that much in the last couple of years. In fact, the last two changes date back years. Mozilla did remove some options including the ability to turn off JavaScript from the preferences back in 2013, and moved the preferences page from its own window to a browser tab in 2014. Mozilla updating Firefox preferences The 2017 update to the preferences page of Firefox will change things around fundamentally, but won't remove any options from the preferences (not that I'm aware of). Note: The development is still in progress. Things may change along the way, Mozilla may move preferences around, create a new category, or make other changes that are not reflected here right now. We will update the article once we become aware of these changes if they happen. If you notice them first, let us know and we update the article asap. The design goals are simple: remove inconsistencies, and improve categories for better navigation. Mozilla did ran some tests and results indicate that the "average success score" improved by 30% over the current implementation. Average success core in this context means whether users managed to complete tasks in the settings successfully, or not. The current implementation of the preferences in the Firefox browser uses the eight tabs general, search, content, application, security, privacy, sync and advanced. Advanced is further divided into the tabs data choices, network, update and certificates. The new design will reduce the number of tabs to the following five: general, downloads & links, privacy & security, Firefox account, and updates. No sub-tabs are used either. This means that some categories, general and privacy & security in particular, will be bigger than before. Take a look at the following mockups which highlight the new layout of the preferences: Note that Firefox Account looks like a new category, but it is just Sync renamed. As far as inconsistencies are concerned; Mozilla plans to remove those as well. To name some: learn more links are placed on the right or next to a preference, search may be next to an item, or on top of it, and options or description fonts may be bold or normal weight. The new preferences make the preferences more compact, as all are listed on five tabs instead of eight (plus four sub-tabs). Mozilla plans to integrate a search option on the preferences page that enables you to find preferences quickly using it. A demo video has been published on YouTube that shows how that search works on Firefox Nightly. Closing Words I prefer less tabs over more tabs when it comes to preferences. Others may prefer it the other way around, especially if the new system requires scrolling to get to certain options. Article source
  16. Mozilla plans to turn on a permissions system for the installation of WebExtensions in the Firefox web browser that is similar to that of Google Chrome. Whenever you install an extension in Google Chrome, all of the extra permissions that the extension requests are listed in the installation prompt. The idea is to provide users with information on these extra permissions, so that abusive extensions can be avoided. The main issue with the permissions system is that most users are probably ignoring the permissions prompt. One reason for that is that it is often difficult to find out whether a permission is really needed for functionality, or if it is simply there for marketing or outright malicious purposes. Firefox's new WebExtensions permission system Mozilla plans to launch similar installation permissions in Firefox 54 at the earliest, but most likely in Firefox 55. Firefox will display the extra permissions an extension requires during installation. The current iteration lists all permissions, but no additional information about them in the interface. The permissions come from the manifest.json file of the extension. If you open it in a plain text editor, or a special json viewer (for instance the json viewer of Firefox), you find them listed under the permissions section. This is true for Chrome and Firefox WebExtensions. Please note that you need to extract the extensions file first to get a listing of files included. Google published a page that lists all optional Chrome permissions that extensions may declare, and Mozilla published one as well. The permissions are not identical at this point in time, and it seems unlikely that they will ever be identical. Mozilla plans to support more APIs, and with that may come extra permissions that only Firefox supports. The installation prompt listing the permissions the extension requires is triggered whenever a WebExtension is installed in Firefox. This includes installations from Mozilla AMO and third-party websites, extensions that get side-loaded, and during upgrades. Firefox users who are interested in the feature can enable it right now. Please note that this landed in Firefox 53 Nightly, and that the permission does not exist by default (yet). If you run at least Firefox 53, you may do the following to enable the permission prompts when installing WebExtensions in the Firefox web browser: Load about:config in the Firefox address bar and hit the Enter-key. Confirm that you will be careful if the warning page opens. Right-click in the main area on about:config, and select New > Boolean. Name that Boolean extensions.webextPermissionPrompts. Set it to true. Any WebExtension installation afterwards triggers the installation prompt that highlights the requested permissions. The main tracking bug for the feature is 1308292. Additional information is provided on Mozilla's Wiki website. While we are at it: check out Firefox's permissions manager, and the new permissions system that Mozilla plans to launch. Article source
  17. Mozilla launched a new TestPilot project for the Firefox web browser yesterday that brings Containers to all versions of the web browser. We talked about the web browser's Containers functionality before in our first look of the feature back in mid 2016. Containers look a lot like Firefox profiles on first glance, but they are different in several characteristics. One of the main differences is that containers run under the same profile. While they do separate certain kinds of data when used, other data is not separated like it is the case if you are using profiles in the Firefox web browser. Basically, many of the bits of data that get transferred or created when you connect to websites are separated, while features such as extensions, bookmarks, or browser preferences are not. This makes Containers less powerful than profiles, but still useful for certain use cases. You can use the to sign in to the same web service multiple times, separate browsing activities by using different containers for activities like shopping, social media, research, or entertainment. The latter can be quite useful to limit tracking or ad retargeting among other things. You can sign in to Gmail for instance, and use Google Search in another container to avoid that the account is linked to the searches. Firefox Containers TestPilot experiment The newly launched Containers experiment of the TestPilot project brings the feature to all versions of Firefox. You do need to install the TestPilot extension first, and then the Containers experiment to make use of the feature. If you move the mouse cursor over the plus icon in the tab bar, you will notice the new container options that you can launch from there in new tabs. Simply move the mouse over the plus, and select one of the available containers that you want to launch. You find the color of the container under the tab as an indicator that the tab has been opened in a particular container. All containers use icons and colors to help you distinguish between them. Since containers separate most site data, you will notice that you are not signed in to any account because of that for instance. The functionality of the experiment is somewhat limited right now. You can edit the four default containers -- personal, work, finance and shopping -- and create your own custom containers as well. A click on the container icon in the main Firefox toolbar lists all containers. You can click on any to open a tab in the selected container. The menu indicates as well if sites are currently opened in selected containers. A click on the arrow icon next to a container opens a list of all sites of that container. From there, you may move the tabs to a new window, or hide the container. Hiding hides all tabs of the selected container until you return to the menu later on to reveal the container again in the browser. The order in which container tabs are displayed in Firefox may be change with a click on the sort button. This moves tabs of any container next to each other in the browser's tab bar. Closing Words Mozilla launched the Containers TestPilot experiment to gather data on usage. The data will certainly play a role when it comes to making a decision on the future of the feature. Will it land in Firefox? I would like to see more functionality added to it prior to that, like the ability to restrict sites to containers, shortcuts to open them quickly, or control over a containers set of saved data. Article source
  18. Mozilla Firefox 52.0 RC 2 Windows en-US: x86: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0-candidates/build2/win32/en-US/Firefox%20Setup%2052.0.exe x64: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0-candidates/build2/win64/en-US/Firefox%20Setup%2052.0.exe Windows All languages: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0-candidates/build2/win32/ https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0-candidates/build2/win64/ Other OS: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0-candidates/build2/ Checksum: SHA512SUMS SHA512SUMS.asc Firefox for Android 52.0 RC: https://download-installer.cdn.mozilla.net/pub/mobile/candidates/52.0-candidates/ Mozilla Firefox 45.8.0 ESR RC 2 Windows en-US: x86: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/45.8.0esr-candidates/build2/win32/en-US/Firefox%20Setup%2045.8.0esr.exe x64: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/45.8.0esr-candidates/build2/win64/en-US/Firefox%20Setup%2045.8.0esr.exe Windows All languages: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/45.8.0esr-candidates/build2/win32/ https://download-installer.cdn.mozilla.net/pub/firefox/candidates/45.8.0esr-candidates/build2/win64/ Other OS: https://download-installer.cdn.mozilla.net/pub/firefox/candidates/45.8.0esr-candidates/build2/ Checksum: SHA512SUMS SHA512SUMS.asc
  19. Edge browser still well behind rivals Chrome and Firefox Windows 10 is growing at a slower pace than anyone expected, and as a direct consequence, Microsoft Edge, which is the new default browser in the operating system, is also having a hard time competing against rivals Google Chrome and Mozilla Firefox. NetMarketShare data for the month of February shows that Edge barely moved the needle last month, while its rivals improved their shares in a more substantial manner. Google Chrome is the world’s number one PC browser with a share of 58.53 percent, so nearly 6 out of 10 computers are running this particular browser at the moment. This is undoubtedly impressive, especially because Chrome is not the default browser on Windows, which is the dominating operating system on the desktop. On the other hand, Microsoft’s Internet Explorer dropped to 19.17 percent, and this is a drop that was more or less expected, especially because the browser is no longer actively improved. Internet Explorer isn’t getting any new features, but only security patches and fixes, with Microsoft focusing entirely on Edge in Windows 10. Microsoft Edge performance The third browser in the charts is Mozilla’s Firefox, which is now running on 11.68 percent of the PCs out there, while Microsoft Edge has approximately half of this share despite Redmond’s rather aggressive push for everyone to switch to Windows 10. Edge is running on 5.55 percent of the PCs, up from 5.48 percent the month before, which shows that its adoption is primarily impacted by the limited availability in Windows 10. Microsoft isn’t planning to release Edge browser on a different platform, with the company saying before the launch of Windows 10 that it first wanted to get the app right on its own operating system and then look beyond this possibility. Microsoft Edge, however, is getting a major pack of improvements in the upcoming Windows 10 Creators Update due in April, including new tab options, such as website previews, plus new extensions that are already available for insiders. Source
  20. mozilla

    Mozilla Acquires Pocket We are excited to announce that the Mozilla Corporation has completed the acquisition of Read It Later, Inc. the developers of Pocket. Mozilla is growing, experimenting more, and doubling down on our mission to keep the internet healthy, as a global public resource that’s open and accessible to all. As our first strategic acquisition, Pocket contributes to our strategy by growing our mobile presence and providing people everywhere with powerful tools to discover and access high quality web content, on their terms, independent of platform or content silo. Pocket will join Mozilla’s product portfolio as a new product line alongside the Firefox web browsers with a focus on promoting the discovery and accessibility of high quality web content. (Here’s a link to their blog post on the acquisition). Pocket’s core team and technology will also accelerate Mozilla’s broader Context Graph initiative. Pocket brings to Mozilla a successful human-powered content recommendation system with 10 million unique monthly active users on iOS, Android and the Web, and with more than 3 billion pieces of content saved to date. In working closely with Pocket over the last year around the integration within Firefox, we developed a shared vision and belief in the opportunity to do more together that has led to Pocket joining Mozilla today. As a result of this strategic acquisition, Pocket will become a wholly owned subsidiary of Mozilla Corporation and will become part of the Mozilla open source project. About Mozilla: Mozilla has been a pioneer and advocate for the open web for more than 15 years. We promote open standards that enable innovation and advance the Web as a platform for all. Today, hundreds of millions of people worldwide use Mozilla Firefox to experience the Web on computers, tablets and mobile devices. For more information, visit www.mozilla.org. About Pocket: Pocket, made by Read It Later, Inc., is the world’s leading save-for-later service. It currently has more than 10 million active monthly registered users and is integrated into hundreds of leading apps including Flipboard and Twitter. Pocket helps people save interesting articles, videos and more from the web for later enjoyment. Once saved to Pocket, content is visible on any device — phone, tablet or computer, online or off. Pocket is available for major devices and platforms including Firefox, Google Chrome, Safari, iOS, Android and Windows. For more information, visit www.getpocket.com/about. Download Pocket visuals: Pocket logo Device Lineup My List on iPhone Article View on iOS Side by Side Source Alternate Article Source: Mozilla Buys Pocket, Signals New Direction for Company
  21. Mozilla Firefox 52.0 RC1 Download RC (Select Language) Installer x32 Installer x64
  22. Mozilla Firefox 52.0 Beta 9 Download Beta (Select Language): Installer x32 Installer x64
  23. TLDR: Firefox caches intermediate CA certificates. A third-party website can infer which intermediates are cached by a user. To do this, it loads content from incorrectly configured hosts (missing intermediate in the provided certificate chain) and observes whether they load correctly (yes: corresponding intermediate was cached, no: it was not). Check out my proof of concept using more than 300 intermediate CAs. This technique can be used to gain a fingerprint for a user but also leaks semantic information (mainly geographical). Since Private Browsing mode does not isolate the cache, it can be used to link a Private Browsing user to her real profile. Furthermore, attackers could force users to visit correctly configured websites with unusal intermediates and thus set a kind of supercookie. This has been reported as #1334485 in the Mozilla bug tracker.] The idea A few months ago, I was sitting in Ivan Ristić’s course »The Best TLS Training in the World« (which I highly recommend, by the way). One thing Ivan was mentioning is the fact that probably the most common misconfiguration in setting up a TLS webserver is forgetting to deliver the complete certificate chain. Let me use some pictures to explain it. Here is the correct case: In case the server is misconfigured, the situation looks as follows: An idea came to my mind: if the behaviour is different depending on the cache, can I observe that from the outside? A quick look around on ssllabs.com for a site with incomplete chain and a <img src=https://brokensite/favicon.ico onload=alert(1) onerror=alert(2)> showed me that this was indeed feasible in Firefox (Chrome and Internet Explorer somehow both magically load the image/site even when the chain is not delivered − possibly using the caIssuer extension?). Interestingly enough, the cached CAs from the main profile were also used in Private Browsing mode. Gathering data Lurking around ssllabs.com to find new hosts with incomplete chains did not sound like a fun idea, and I guess Qualys would not have been too happy if I automated the process. So I had to come up with a better way to gather hosts for a proof of concept. Luckily, there are public datasets of the TLS server landscape available. The two that I ended up using were the Censys.io scan (free researcher account needed) and the Rapid7 Project Sonar (free to download) ones. In the first step, I wanted to identify all possible intermediate CA certificates that chain up to a trusted root CA. For this, I downloaded the Root CA extract provided by the curl project. Then I looked at all CA certificates in the datasets and checked with openssl verify to see if they are a direct intermediate of one of the trusted roots. To further identify intermediate CAs that chain up to a trusted root in a longer path, I ran this process in an iterative fashion using the root CAs and already identified intermediates until no more new intermediates were found in the datasets. I ended up with 3366 individual CA certificates that chain up to a trusted root (1931 on the first level, 1286 on the second level, 92 on the third level and 57 on the fourth level). The next step was identifying websites which were misconfigured. For this, the Project Sonar data came in handy as they scan the complete IPv4 internet and record the delivered certificate chain for each IP on port 443. Since they provide the certificates individually and the scan data only contains hashes of the chain elements, I first had to import all the certificates into a SQLite database in order to quickly look them up by hash. Despite ending up with a database file of roughly 100 GB, SQLite performed quite nicely. I then processed this data by looking at all certificates to see if they contained an issuer (by looking at the Authority Key Identifier extension) that was present in my set of CAs, but not delivered in the chain. If this was the case, I had identified the IP address of a misconfigured host. Now it was necessary to see if the certificate used a hostname which actually resolved to that IP address. If that was the case, I had a candidate for an incorrectly configured webserver. The last step was to identify a working image on that webserver which can be loaded. I considered several options but settled on just loading the website in Firefox and observing using Burp which images were loaded. This left me with a Burp state file of several gigabytes and a list of plenty of URLs for more than 300 individual intermediate CAs. The proof of concept I used this list of URLs to build a proof of concept using elm, my favourite way to avoid writing JavaScript these days. Here is how a part of the output (and Firebug’s Net Panel to see which images are loaded) looks for me: Note that it might occasionally contain false positives or false negatives, since the servers that are used for testing are not under my control and might change their TLS configuration and/or location of images. If you run the proof of concept yourself, you will be presented with an option to share your result with me. Please do so − I am grateful for every data point obtained in this way to see what additional information can be extracted from it (geographical location? specific interests of the user? etc.). Further ideas One thing that is pretty easy to see is that this technique could also be used in a more active way by forcing users to visit correctly configured websites from unusual intermediates. Note that for example the PKI of the »Deutsches Forschungsnetzwerk« comes in handy here, as it provides literally hundreds of (managed) intermediates for their members, including lots of tiny universities or research institutes. One could force to user to cache a certain subset of unusal intermediates and then check later from a different domain which intermediates are set. This is of course not foolproof, since users might visit correctly configured websites from those intermediates and thus flip bits from 0 to 1. Error-correcting codes could be used here (with the tradeoff of having to use more intermediates) to deal with that problem. In addition to the purely »statistical« view of having a fingerprint with a sequence of n bits representing the cache status for each tested CA, the fingerprint also contains additional semantic information. Certain CAs have customers mostly in one country or region, or might have even more specific use-cases which let’s you infer even more information − i.e. a user who has the »Deutsche Bundestag CA« cached is most probably located in Germany and probably at least somewhat interested in politics. From an attacker’s perspective, this could also be used to check if the browser is running inside a malware analysis sandbox (which would probably have none or very few of the common intermediates cached) and delivering different content based on that information. Solutions I reported the problem on January 27th, 2017 to Mozilla in bug #1334485. The cleanest solution would obviously be to not connect to incorrectly configured servers, regardless of whether the intermediate is cached or not. Understandably, Mozilla is reluctant to implement that without knowing the impact. Thus bug #1336226 has been filed to implement some related telemetry − let’s see how that goes. From a user’s perspective, at the moment I can only recommend to regularly clean up your profile (by creating a fresh one, cleaning it up from the Firefox UI or using the certutil command line tool). Alternatively, blocking third-party requests with an addon such as Request Policy might be useful since the attack obviously needs to make (a lot of) third-party requests. By Alexander Klink https://shiftordie.de/blog/2017/02/21/fingerprinting-firefox-users-with-cached-intermediate-ca-certificates-fiprinca/
  24. Mozilla Firefox 52.0 Beta 8 Download Page-Beta: https://www.mozilla.org/en-US/firefox/beta/all/ Windows en-US: x86: https://download-installer.cdn.mozilla.net/pub/firefox/releases/52.0b8/win32/en-US/Firefox Setup 52.0b8.exe x64: https://download-installer.cdn.mozilla.net/pub/firefox/releases/52.0b8/win64/en-US/Firefox Setup 52.0b8.exe Windows All languages: https://download-installer.cdn.mozilla.net/pub/firefox/releases/52.0b8/win32/ https://download-installer.cdn.mozilla.net/pub/firefox/releases/52.0b8/win64/ Checksum: SHA512SUMS SHA512SUMS.asc Release Notes[Beta]: https://www.mozilla.org/en-US/firefox/beta/notes/ Firefox for Android 52.0 Beta 8: https://download-installer.cdn.mozilla.net/pub/mobile/releases/52.0b8/ To download beta candidates(build 1): https://download-installer.cdn.mozilla.net/pub/firefox/candidates/52.0b8-candidates/build1/ Android beta candidates(build 1): https://download-installer.cdn.mozilla.net/pub/mobile/candidates/52.0b8-candidates/build1/
  25. The year 2017 is an important one for Mozilla and Firefox. Multi-process will be enabled for all users of the web browser, sandboxing is introduced, the first bits of Project Quantum are integrated into the web browser, and the add-on system will be switched exclusively to WebExtensions. Mozilla revealed an updated add-ons roadmap yesterday that highlights major milestones on the way to making Firefox WebExtensions exclusive. We talked about Mozilla's plans for Firefox in this regard before. WebExtensions is a set of APIs that developers can utilize to create add-ons for browsers. Firefox is not the only browser to use WebExtensions, as others, Chrome, Opera and Edge, use the system as well. That's good for cross-browser development, better for Mozilla's add-ons review process, better for add-on compatibility with future Firefox versions, and probably also better for browser stability. Firefox Add-ons Roadmap for 2017 WebExtensions is a good addition to Firefox, and most Firefox users who criticize Mozilla are not doing it because of the integration, but because of Mozilla's plans for the browser's legacy add-on systems. Mozilla plans to cut all ties to those add-on systems. This means that legacy add-ons won't run in Firefox anymore when the plug is pulled. Legacy add-ons, as defined by Mozilla, are all extensions that are not WebExtensions. This includes anything with XUL, bootstrapped extensions, SDK extensions, embedded WebExtensions, and complete themes. Language packs, dictionary files, OpenSearch providers, lightweight themes, and add-ons that are exclusively available for Thunderbird or SeaMonkey are not considered legacy by Mozilla. Any legacy add-on that is not ported by its author to WebExtensions -- if that is possible -- will no longer work in Firefox 57. A big issue that developers face right now is that WebExtensions is a work in progress. Not all APIs are available yet, and some APIs that are required for certain legacy add-on features may never make it into Firefox. This has caused some developers to quit development, or paint a grim picture in regards to the future of their add-ons. The Roadmap See Firefox release schedule for release dates. Firefox 53: April 18, 2017 New legacy add-ons won't be accepted anymore on AMO (addons.mozilla.org). Updates to existing add-ons are still accepted. Add-ons may only load binaries if they use the Native Messaging API. Multi-process is on by default for all users. Only exception for systems with add-ons that state explicitly that they are not compatible with multi-process. Firefox 54 to 56: June 13, 2017 to October 3, 2017 Mozilla launches multiple content process for E10s in Firefox 55 and security sandboxing in Firefox 54. This may impact some legacy add-ons. Firefox 57: November 28, 2017 Legacy add-ons are no longer supported. Firefox won't load legacy add-ons anymore. Firefox 57 is WebExtensions exclusive- Multi-process compatibility shims are removed from Firefox. Legacy add-ons remain on AMO for the time being. Mozilla has yet to announce a deadline for end of support for these listings (the listings may still be updated for instance) Closing Words It is too early to conclude how the move will affect Firefox's add-ons ecosystem. Some developers announced that they won't migrate to WebExtensions already, and the same is certainly true for add-ons that are no longer in development but still working right now. Some of these may be ported by other authors, and there will certainly be an increase of Chrome extension ports to Firefox. Also, most Chrome extensions will work in Firefox eventually when Firefox reaches parity with Chrome in regards to WebExtensions APIs. WebExtensions will limit Firefox add-ons in regards to what they can do to the browser. Article source