Mozilla, Gecko Archive

Continuing our past work, Firefox 60 brings further important improvements to security sandboxing on Linux, making it harder for attackers that find security bugs in the browser to escalate those into attacks against the rest of the system.

The most important change is that content processes - which render Web pages and execute JavaScript - are no longer allowed to directly connect to the Internet, or connect to most local services accessed with Unix-domain sockets (for example, PulseAudio).

This means that content processes have to follow any network access restrictions Firefox imposes - for example, if the browser has been set up to use a proxy server, connecting directly to the internet is no longer possible. But more important are the restrictions on connections to local services: they often assume that anything connecting to them has the full authority of the user running it, and either allow it to ask for arbitrary code to run, or aren't careful about preventing that. Normally that's not a security problem because the client could just run that code itself, but if it's a sandboxed Firefox process, that could have meant a sandbox escape.

Content on the web is powerful. It enables us to learn new things, discover different perspectives, stay in touch with what's happening in the world, or just make us laugh. Making sure that stories like these - stories that are worth your time and attention - are discoverable and supported is central to what we care about at Pocket.

It's important for quality content like this to thrive - and a critical way it's funded is through advertising. But unfortunately, today, this advertising model is broken. It doesn't respect user privacy, it's not transparent, and it lacks control, all the while starting to move us toward low quality, clickbait content.

We believe the Internet can do better. So earlier this year, we started to explore a new model and showed an occasional sponsored story in Pocket's recommendation section on Firefox New Tab. Starting today, we're expanding this work further - now Firefox Nightly and Beta users may also see these sponsored stories. We're preparing for this feature to go fully live in May to Firefox users in the US with the Firefox 60 release.

For a long time, it was just setting the default search provider to Google in exchange for a beefy stipend. Later, paid links in your new tab page were added. Then, a proprietary service, Pocket, was bundled into the browser - not as an addon, but a hardcoded feature. In the past few days, we’ve discovered an advertisement in the form of browser extension was sideloaded into user browsers. Whoever is leading these decisions at Mozilla needs to be stopped.

People have noticed that Firefox is fast again.

Over the past seven months, we’ve been rapidly replacing major parts of the engine, introducing Rust and parts of Servo to Firefox. Plus, we’ve had a browser performance strike force scouring the codebase for performance issues, both obvious and non-obvious.

We call this Project Quantum, and the first general release of the reborn Firefox Quantum comes out tomorrow.

orthographic drawing of jet engine

But this doesn’t mean that our work is done. It doesn’t mean that today’s Firefox is as fast and responsive as it’s going to be.

So, let’s look at how Firefox got fast again and where it’s going to get faster.

PDFium is the Google open-source project for PDF support in Google Chrome. PDFium was previously closed-source based upon Foxit PDF technology while now it's been fully open-source since 2014.

The Pepper API Flash implementation is also what's used by Google's Chrome web-browser. By switching to the PAPI-based Flash, Firefox would be able to finish getting rid of their NPAPI support with the Firefox Flash support still relying upon it with Shumway and other projects not panning out.

By the end of 2015 Mozilla leadership had come to the conclusion that our then Firefox OS initiative of shipping phones with commercial partners would not bring Mozilla the returns we sought. We made the first of a series of announcements about changes in the development of Firefox OS at Mozilla. Since then we have gradually wound down that work and, as of the end of July 2016 have stopped all commercial development on Firefox OS. This message recaps what transpired during that period of time and also describes what will happen with the Firefox OS code base going forward.

We need competition; we also need diversity. We need the possibility that young, game-changing market entrants might come along. We need that idea to be kept alive, to make sure that all the browsers don't shift from keeping users happy to just keeping a few giant corporations that dominate the Web happy. Because there's always pressure to do that, and if all the browsers end up playing that same old game, the users will always lose.

We need more Firefoxes.

We need more browsers that treat their users, rather than publishers, as their customers. It's the natural cycle of concentration-disruption-renewal that has kept the Web vibrant for nearly 20 years (eons, in web-years).

We may never get another one, though.

Farewell Firefox OS smartphones. Mozilla today announced an end to its smartphone experiment, and said that it would stop developing and selling Firefox OS smartphones. It will continue to experiment on how it might work on other connected devices and Internet of Things networks.

Firefox for iOS lets you take your favorite browser with you wherever you go with the Firefox features you already love including smart and flexible search, intuitive tab management, syncing with Firefox Accounts and Private Browsing.

Today we are announcing some major upcoming changes to Firefox add-ons. Our add-on ecosystem has evolved through incremental, organic growth over the years, but there are some modernizations to Firefox that require some foundational changes to support.

Mozilla has revamped its Firefox OS mobile software project after concluding that ultra-affordable $25 handsets aren't enough to take on the biggest powers of the smartphone world, CNET has learned.

Panasonic Smart TVs powered by Firefox OS are optimized for HTML5 to provide strong performance of Web apps and come with a new intuitive and customizable user interface which allows quick access to favorite channels, apps, websites and content on other devices. Through Mozilla-pioneered WebAPIs, developers can leverage the flexibility of the Web to create customized and innovative apps and experiences across connected devices.

Firefox OS is coming to Japan and doing it in style.

Announced at a KDDI press event in Tokyo today, the Fx0 is a striking 4.7-inch smartphone with a transparent shell and a home button decorated with the golden Firefox logo embracing the Earth. It runs the latest version of Mozilla's web-centric mobile OS and was designed by noted Japanese designer Tokujin Yoshioka, whose previous collaboration with KDDI produced a phone worthy of making it into the Museum of Modern Art's collection. With the Fx0, Yoshioka has worked around the familiar outlines of LG's G3 design (LG is the silent partner producing the device) and adapted them to a smaller size while producing a delightful aesthetic in the process. Like a watch with a window showing its internal mechanism, this phone's exposed electronics are a subtle reminder of its technical sophistication - plus, that Firefox home button is just plain cool.

If you're visiting any Yahoo property today, chances are you'll see an "Upgrade to the new Firefox" link in the top-right corner of your browser window. The prompt also appears if you're using Internet Explorer, Opera and even the new Yandex browser. However, the prompt is missing from Safari, which will surely prompt a new round of speculation about Apple's rumored switch to Yahoo as its default search engine.

Given that Firefox now uses Yahoo as its default search engine, this move doesn't come as a huge surprise. Yahoo clearly wants as many people as possible to use Firefox - and with it its search engine (which is powered by Microsoft Bing).