RoccamOccam writes: WebRender, an experimental GPU-based renderer for web content, written in Rust, is now enabled by default for Firefox Nightly users on desktop Windows 10 with Nvidia GPUs. The announcement was made on the mailing list.

Lin Clark provides an excellent overview of WebRender and, states, "with WebRender, we want apps to run at a silky smooth 60 frames per second (FPS) or better no matter how big the display is or how much of the page is changing from frame to frame. And it works. Pages that chug along at 15 FPS in Chrome or today's Firefox run at 60 FPS with WebRender.

In describing the WebRender approach Clark, asks, "what if we removed this boundary between painting and compositing and just went back to painting every pixel on every frame? This may sound like a ridiculous idea, but it actually has some precedent. Modern day video games repaint every pixel, and they maintain 60 frames per second more reliably than browsers do. And they do it in an unexpected way instead of creating these invalidation rectangles and layers to minimize what they need to paint, they just repaint the whole screen."

Back in 2014, Mozilla partnered with Bing to translate webpages via Firefox in a similar fashion to Chrome's implementation of Google Translate. The company also added support for Yandex Translate in Firefox 41 in mid-2015, but it went all dark soon after and very few updates were issued. Now, Mozilla is finally starting to add support for Google Translate to the translation engine built into Firefox. gHacks reports: While the feature is not fully functional yet, it is an indicator that Mozilla has not forgotten the translate feature completely. Users who enable the translate functionality in Firefox on about:config will notice that Google is the selected translation engine. Google Translate cannot be used currently in Firefox; the browser throws an error message when you hit the translate button in the UI. Bing and Yandex don't seem to work either at this point in time even though Firefox seems to try and translate the page. The "there has been an error translating this page" error is thrown eventually as well. Google Translate requires API access keys and that is usually only available if companies or users pay for the key. It is unclear if Mozilla plans to make a deal with Google or if users will be required to use their own API keys for the functionality. The latter would surely be very limiting.

The Tor Browser has rolled out a new interface with the release of v8. From a report: The Tor Browser has always been based on the Firefox codebase, but it lagged behind a few releases. Mozilla rolled out a major overhaul of the Firefox codebase in November 2017, with the release of Firefox 57, the first release in the Firefox Quantum series. Firefox Quantum came with a new page rendering engine, a new add-ons API, and a new user interface called the Photon UI. Because these were major, code-breaking changes, it took the smaller Tor team some time to integrate all of them into the Tor Browser codebase and make sure everything worked as intended. The new Tor Browser 8, released yesterday, is now in sync with the most recent version of Firefox, the Quantum release, and also supports all of its features. This means the Tor Browser now uses the same modern Photon UI that current Firefox versions use, it supports the same speed-optimized page rendering engine and has also dropped support for the old XUL-based add-ons system for the new WebExtensions API system used by Chrome, Opera, Vivaldi, Brave, and the rest of the Chromium browsers.

An anonymous reader writes: Mozilla today released Firefox 62 for Windows, Mac, Linux, and Android. The release builds on Firefox Quantum, which the company calls "by far the biggest update since Firefox 1.0 in 2004." Version 62 brings variable fonts, automatic dark theme on macOS, and better scrolling on Android. Firefox 62 for the desktop is available for download now on Firefox.com, and all existing users should be able to upgrade to it automatically. As always, the Android version is trickling out slowly on Google Play. The latest iOS version is available on Apple's App Store.

Google first released its Chrome browser 10 years ago today. Marketed as a "fresh take on the browser," Chrome debuted with a web comic from Google to mark the company's first web browser. From a report: It was originally launched as a Windows-only beta app before making its way to Linux and macOS more than a year later in 2009. Chrome debuted at a time when developers and internet users were growing frustrated with Internet Explorer, and Firefox had been steadily building momentum. Google used components from Apple's WebKit rendering engine and Mozilla's Firefox to help bring Chrome to life, and it made all of Chrome's source code available openly as its Chromium project. Chrome focused on web standards and respected HTML5, and it even passed both the Acid1 and Acid2 tests at the time of its release. This was a significant step as Microsoft was struggling to adhere to open web standards with its Internet Explorer browser.

Another significant part of Chrome's first release was the idea of "sandboxing" individual browser tabs so that if one crashed it wouldn't affect the others. This helped improve the speed and stability of Chrome in general, alongside Google's V8 JavaScript engine that the company constantly tweaked to try and push the web forwards. After a decade of Chrome, this browser now dominates as the primary way most people browse the web. Chrome has secured more than 60 percent of browser market share on desktop, and Google's Chrome engineers continue to improve it with new features and push the latest web standards. To mark the milestone, Google said it would make a surprise announcement on Tuesday -- some improvements coming to Chrome.

Google's curvy tab Material Design update for Chrome will arrive in version 69 of the browser due out in September. From a report: Google flags the upcoming changes in its Enterprise release notes for Chrome 69, which gives a brief mention under browser interface changes to a "new design across all operating systems." Chrome 69, penciled in for stable release on September 4, will also get native Windows 10 notifications, which have been rolling out to users over the past month. Chrome 69 will also progress the long-running project to deprecate Flash Player, which Adobe has announced will reach end of life in 2020. Microsoft, Mozilla, and Apple have similar deprecation timelines for Flash on their desktop browsers. Once ubiquitous, Flash content is now hardly used at all by Chrome users, though Google won't fully remove support until Chrome 87 in 2020. At present, if a user enables Flash for a particular site, they don't need to approve it if they visit the site again. However, in Chrome 69, every time users restart Chrome, they'll need to give permission for sites to use Flash.

Mozilla announced today plans to remove all Firefox legacy add-ons from the official Mozilla add-ons portal in early October. From a report: The move comes after Mozilla updated the Firefox core to use a new add-ons system based on the Chrome-compatible WebExtensions API. This new add-ons API replaced Firefox's old XUL-based add-ons API in November 2017, with the release of Firefox 57. All Firefox legacy add-ons stopped working in Firefox 57, but Mozilla continued to support them in the Firefox Extended Support Release (ESR) 52 branch. Support for Firefox ESR 52 will end on September 5, in two weeks, meaning there won't be any official Firefox version that supports legacy add-ons anymore.

An anonymous reader quotes a report from Reuters: A group of 22 state attorneys general and the District of Columbia late Monday asked a U.S. appeals court to reinstate the Obama administration's 2015 landmark net neutrality rules and reject the Trump administration's efforts to preempt states from imposing their own rules guaranteeing an open internet. The states argue the FCC reversal will harm consumers. The states also suggested the FCC failed to identify any "valid authority" for preempting state and local laws that would protect net neutrality. The FCC failed to offer a "meaningful defense of its decision to uncritically accept industry promises that are untethered to any enforcement mechanism," the states said.

The state attorney generals suing represent states with 165 million people -- more than half the United States population -- and include California, Illinois, New Jersey, North Carolina, Pennsylvania and Virginia. The states argue the FCC action could harm public safety, citing electrical grids as an example. They argue "the absence of open internet rules jeopardizes the ability to reduce load in times of extreme energy grid stress. Consequently, the order threatens the reliability of the electric grid." Several internet companies also filed a legal challenge to overturn the FCC ruling, including Mozilla, Vimeo, Etsy, and numerous media and technology advocacy groups, reports Reuters. The group of 22 state attorneys general first filed their lawsuit in January after the Trump administration voted to repeal the net neutrality rules in December.

Long-time Slashdot reader tdailey spotted a new version of Pale Moon, a customised version of Firefox optimized for speed and efficiency. Beta News reports it's the first major update since November of 2016:

There are virtually no visual or obvious changes in this new major build, but the under-the-hood changes are both extensive and necessary.... Despite all the updates, Moonchild is keen to stress certain things haven't changed -- unlike Firefox, for example, Pale Moon continues to support NPAPI plugins, complete themes and a fully customizable user interface. There is also no DRM built into the browser, although third-party plugins such as Silverlight are supported. It will also continue to work with certain "legacy" plugins of the type abandoned by Firefox.
Pale Moon strips out what one reviewer calls "little-used components" of Firefox, including parental controls and accessbility features, as well as crash reports and support for Internet Explorer's ActiveX and ActiveX scripting technology.

"Proving that open source leads to great development, Pale Moon takes the already decent Firefox web browser and makes it even better and a faster."

An anonymous reader writes: Mozilla has removed 23 Firefox add-ons from its add-on store that snooped on users and sent data to remote servers, a Mozilla engineer told Bleeping Computer Friday. The list of blocked add-ons includes "Web Security," a security-centric Firefox add-on with over 220,000 users, which was at the center of a controversy this week after it was caught sending users' browsing histories to a server located in Germany. "The mentioned add-on has been taken down, together with others after I conducted a thorough audit of [the] add-ons," Rob Wu, a Mozilla Browser Engineer and Add-on review, told Bleeping Computer via email. "These add-ons are no longer available at AMO and [have been] disabled in the browsers of users who installed them," Wu said.

Mozilla on Tuesday began testing a Firefox extension that shows you its best guesses for what you want to see on the web. From a report: The Advance web extension is available for anyone from today and can analyze content on current active web pages to recommend related tidbits you may want to "read next" from other websites. It will also surface recommendations based on your recent browsing history in a "for you" section. With the extension installed, you just browse the web as you normally would and the little sidebar will show things that are relevant to what you've been looking at. The extension is powered by Laserlike, a VC-funded, machine learning-powered "interest search engine" that delivers personalized content. As such, Laserlike will receive users' browsing history -- something Mozilla wants people to understand before they install the extension. But the company has also built in some tools to boost control and data transparency.

Let's Encrypt has announced that it is now directly trusted by all major root certificates including those from Microsoft, Google, Apple, Mozilla, Oracle, and Blackberry. With this announcement, Let's Encrypt is now directly trusted by all major browsers and operating systems. From a report: While Let's Encrypt has already been trusted by almost all browsers, it was done so through intermediate certificate that were cross-signed by IdenTrust. As IdenTrust was directly trusted by all major browser vendors and operating systems, it also allowed Let's Encrypt to be trusted as well. With Let's Encrypt now being directly trusted, if there is ever a problem with IdenTrust and they themselves become untrusted, Let's Encrypt users will still be able to function properly.

With their next patch Mozilla will introduce two new features to their Firefox browser they call "DNS over HTTPs" (DoH) and Trusted Recursive Resolver (TRR). Mozilla says this is an additional feature which enables security. Researchers think otherwise. From a report: So let's get to the new Firefox feature called "Trusted Recursive Resolver" (TRR). When Mozilla turns this on by default, the DNS changes you configured in your network won't have any effect anymore. At least for browsing with Firefox, because Mozilla has partnered up with Cloudflare, and will resolve the domain names from the application itself via a DNS server from Cloudflare based in the United States. Cloudflare will then be able to read everyone's DNS requests.

From our point of view, us being security geeks, advertising this feature with slogans like "increases security" is rather misleading because in many cases the opposite is the case. While it is true that with TRR you may not expose the websites you call to a random DNS server in an untrustworthy network you don't know, it is not true that this increases security in general. It is true when you are somewhere in a network you don't know, i. e. a public WiFi network, you could automatically use the DNS server configured by the network. This could cause a security issue, because that unknown DNS server might have been compromised. In the worst case it could lead you to a phishing site pretending to be the website of your bank: as soon as you enter your personal banking information, it will be sent straight to the attackers.

But on the other hand Mozilla withholds that using their Trusted Recursive Resolver would cause a security issue in the first place for users who are indeed in a trustworthy network where they know their resolvers, or use the ISP's default one. Because sharing data or information with any third party, which is Cloudflare in this case, is a security issue itself.

This week the Internet Archive hosted an amazing Decentralized Web Summit, which united the makers who want to build a web "that's locked open for good." [Watch the videos here.] Vint Cerf was there, as was the technical product development leader for Microsoft's own decentralized identity efforts, several companies building the so-called punk rock Internet, "along with a handful of venture capitalists looking for opportunities." One talk even included Mike Judge, the creator of HBO's Silicon Valley, which recently included the decentralized web in its ongoing storyline.

Computing highlighted remarks by Brewster Kahle, the founder of the Internet Archive, and Mitchell Baker, the chairperson of the Mozilla Foundation. The ideology of the web's early pioneers, according to Baker, was free software and open source. "Money was considered evil," she said. So when companies came in to commercialize the internet, the original architects were unprepared. "Advertising is the internet's original sin," Kahle told the packed room. "Advertising is winner-take-all, and that's how we've ended up with centralization and monopolies."

At the conference, attendees presented utopian visions of how the future of the internet could look. Civil, a new media startup, proposed crowd-supported journalism using cryptocurrency micro-payments. Mastodon, a decentralized and encrypted social network, was commonly referenced as an alternative to Twitter. As Facebook and Google continue to monopolize the digital advertising ecosystem -- recent estimates say that the two companies control over 70% of digital advertising spending globally -- the promise of a decentralized web, free from the shackles of advertiser demands is fun to imagine.
Tristan Harris, who leads the Center for Humane Technology, "just hopes the pioneers of the new internet turn around to face the potential negative externalities of their products before it's too late," arguing that "If we decentralize the systems we already have without an honest recognition of the social harms that are being created -- mental health [issues], loneliness, addiction, polarization, conspiracy theories... then we've decentralized social harms and we can't even track them." But Tim Berners-Lee "remains hopeful".

"There's massive public awareness of the effects of social networks and the unintended consequences," he told Computing. "There's a huge backlash from people wanting to control their own data"... Meanwhile, there's the rise of "companies which respect user privacy and do not do anything at all with user data" (he namechecks social network MeWe to which he acts as an advisor), open-source collaborations like the data portability project (DTP) led by tech giants, and his own project Solid which is "turning from an experiment into a platform and the start of a movement".

"These are exciting times," said Berners-Lee.

An anonymous reader writes: Mozilla is rebranding Firefox. The company is asking for feedback on the new look, which will try to cover the various Firefox offerings. For most people, Firefox refers to a browser, but the company wants the brand to encompass all the various apps and services that the Firefox family of internet products cover, "from easy screenshotting and file sharing to innovative ways to access the internet using voice and virtual reality." The fox with a flaming tail "doesn't offer enough design tools to represent this entire product family," Mozilla believes.

An anonymous reader writes: "The Mozilla Foundation, the organization behind the Firefox browser, is working on adding a new feature to its browser that is similar to the Site Isolation feature that Google rolled out to Chrome users this year," reports Bleeping Computer. "[Chrome's] Site Isolation works by opening a new browser process for any domain/site the user loads in a tab." The feature has been recently rolled out to 99% of the Chrome userbase. "But Chrome won't be the only browser with Site Isolation," adds Bleeping Computer. "Work on a similar feature also began at Mozilla headquarters back in April, in a plan dubbed Project Fission." Mozilla engineers say that before rolling out Project Fission (Site Isolation), they need to optimize Firefox's memory usage first. Work has now started on shaving off 7MB of RAM from each Firefox content process in order to bring down per-process RAM usage to around 10MB, a limit Mozilla deems sustainable for rolling out Site Isolation.

An anonymous reader shares a report: Mozilla engineers are preparing to remove one of the Firefox browser's oldest features -- its built-in support for RSS and Atom feeds, and inherently, the "Live Bookmarks" feature. All Firefox users are probably well accustomed to this feature, albeit not many have ever used it. This feature powers the browser's ability to detect when users are accessing an RSS/Atom feed and then show a special page that lets them subscribe to the feed with a custom feed reader or the browser's built-in "Live Bookmarks" feature. [...] In a recent discussion on the company's bug tracker, Mozilla engineers said they plan to remove feed support sometime later this year, with the release of Firefox 63 or Firefox 64 --scheduled for October and December, respectively.

Usama Jawad, writing for Neowin: Early last year, YouTube received a design refresh with Google's own Polymer library which enabled "quicker feature development" for the platform. Now, a Mozilla executive is claiming that Google has made YouTube slower on Edge and Firefox by using this framework. In a thread on Twitter, Mozilla's Technical Program Manager has stated that YouTube's Polymer redesign relies heavily on the deprecated Shadow DOM v0 API, which is only available in Chrome. This in turn makes the site around five times slower on competing browsers such as Microsoft Edge and Mozilla Firefox. Further reading: Safari Users Unable to Play Newer 4K Video On YouTube in Native Resolution.

Mozilla's latest Nightly builds for Firefox now include an option to mute autoplaying audio. The feature was recently added to the Chrome browser, but Mozilla's update offers a few more options. According to Engadget, "You can turn the feature off entirely, force it to ask for permission, and make exceptions for specific sites." Keep in mind that these are nightly releases, so you will most likely run into some bugs. The "polished version" is likely weeks away.

An anonymous reader quotes VentureBeat: It's been more than 20 months since our last browser benchmark battle, and we really wanted to avoid letting two years elapse before getting a fresh set of a results. Google Chrome, Mozilla Firefox, and Microsoft Edge have all improved significantly over the past year and a half, and as I've argued before, the browser wars are back. You can click on the individual test to see the results:

SunSpider: Edge wins!
Octane: Chrome wins!
Kraken: Firefox wins!
JetStream: Edge wins!
MotionMark: Edge wins!
Speedometer: Chrome wins!
BaseMark: Chrome wins!
WebXPRT: Firefox wins!
HTML5Test: Chrome wins!

Chrome looks to be ahead of the pack according to these tests. That said, browser performance was solid across all three contestants, and it shouldn't be your only consideration when picking your preferred app for consuming internet content.
Chrome wins in four tests, beating Edge's three wins, and Firefox's two wins.