# Mozilla Mozilla is an organization associated with Firefox browsers, MDN, developer resources, and security tools. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Firefox 157 Beta Released With Latest Enhancements DevFeed: [Firefox 157 Beta Released With Latest Enhancements]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-15T12:31:03Z Content type: release Language: en Sources: [Phoronix]() Topics: [Firefox](), [Mozilla](), [CSS](), [Nova](), [Playback](), [HTML](), [ui]() Tags: [audio](), [css](), [desktop-linux](), [firefox](), [html](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [mozilla](), [nova](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [playback](), [release](), [ubuntu-benchmarks](), [ubuntu-hardware](), [ui]() ### AI overview Firefox 157 Beta adds improved HDR video handling for 8-bit formats, better audio/video synchronization when playback speed changes, and fixes for the vertical tabs sidebar. It also adds CSS support for the @supports at-rule function and the "chain" value for the CSS overscroll-behavior property, alongside Nova UI design work and the return of compact mode. ### Source excerpt The Firefox release train keeps on rolling. With Firefox 156 released, Firefox 157 is now in beta ahead of the planned release coming up at the end of September... ## Firefox 156 Available With Its Built-In PDF Viewer Starting Up To 45% Faster DevFeed: [Firefox 156 Available With Its Built-In PDF Viewer Starting Up To 45% Faster]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-14T15:09:09Z Content type: news Language: en Sources: [Phoronix]() Topics: [Firefox](), [pdf](), [Mozilla](), [Linux](), [Nvidia]() Tags: [cpu](), [desktop-linux](), [firefox](), [history](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [memory](), [mozilla](), [nvidia](), [open-source-graphics](), [pdf](), [performance](), [phoronix](), [phoronix-test-suite](), [release](), [ubuntu-benchmarks](), [ubuntu-hardware](), [update](), [vulkan]() ### AI overview Firefox 156 is available with a built-in PDF viewer that starts up up to 45% faster. The release also improves memory and CPU usage when displaying large scaled-down JPEG images and includes several fixes. Vulkan Video decoding for newer NVIDIA GPUs remains limited to nightly builds. ### Source excerpt Mozilla today published their Firefox 156.0 release binaries ahead of the official Tuesday announcement... ## exploits.club Weekly Newsletter 80 - ITW Windows Bugs, Deterministic iOS Exploits, Pwn2Own Firefox Vulns, and More DevFeed: [exploits.club Weekly Newsletter 80 - ITW Windows Bugs, Deterministic iOS Exploits, Pwn2Own Firefox Vulns, and More]() Original publisher: [Read original article]() Author: exploits.club Published: 2025-07-24T15:21:15Z Content type: news Language: en Sources: [exploits.club]() Topics: [iOS](), [Firefox](), [Windows](), [bug](), [Exploit](), [Kernel](), [Fuzzing/Fuzz testing](), [IO](), [Mozilla]() Tags: [bugs](), [cve](), [exploits](), [firefox](), [fuzzing](), [ios](), [kernel](), [love](), [windows]() ### AI overview This issue of exploits.club Weekly Newsletter reviews recent security research and resources, including white-box fuzzing with AFL++, deterministic iOS kernel exploits extended to additional chipsets, an analysis of the Windows vulnerability CVE-2025-29824 and its use in the wild, and a Mozilla Firefox vulnerability discussed in connection with Pwn2Own. ### Source excerpt The Cameraman at that Coldplay concert pic.twitter.com/MHtqBxbwC6 -- Hater Report (@HaterReport_) July 18, 2025 Annnnnnnyways 👇 80 NEWSLETTERS 🎉 In Case You Missed It... Fuzzing 1001: Introductory white-box fuzzing with AFL++ - new course from OST2! Pwnie Nominees for 2025 - Released this week. Check them out!! Resources ## Introducing Uniffi for React Native: Rust-Powered Turbo Modules DevFeed: [Introducing Uniffi for React Native: Rust-Powered Turbo Modules]() Original publisher: [Read original article]() Author: Mark Mayo Published: 2024-12-04T19:38:01Z Content type: article Language: en Sources: [Mozilla Hacks - the Web developer blog]() Topics: [React Native](), [Rust](), [cross-platform](), [Mozilla](), [Open Source](), [JavaScript](), [Process]() Tags: [c-plus-plus](), [cross-platform](), [developer-tools](), [featured-article](), [firefox](), [javascript](), [memory-safety](), [mozilla](), [open-source](), [performance](), [react](), [react-native](), [rust]() ### AI overview Mozilla and Filament introduce Uniffi for React Native, an open-source tool for building React Native Turbo Modules in Rust. It generates bindings that let developers use Rust for shared core logic across iOS and Android, helping address JavaScript-thread performance limits while avoiding duplicated platform code or more difficult C++ integration. ### Source excerpt Mozilla and Filament have introduced Uniffi for React Native, a tool that allows developers to leverage the safety and performance benefits of Rust in cross-platform React Native apps. The post Introducing Uniffi for React Native: Rust-Powered Turbo Modules appeared first on Mozilla Hacks - the Web developer blog. ## Introducing the MDN HTTP Observatory DevFeed: [Introducing the MDN HTTP Observatory]() Original publisher: [Read original article]() Author: hermina-condei Published: 2024-07-02T00:00:00Z Content type: article Language: en Sources: [MDN Blog]() Topics: [Security](), [HTTP](), [Web](), [Documentation](), [migration](), [Testing](), [Mozilla](), [Architecture & Design]() Tags: [audits](), [best-practices](), [blog](), [blog-post](), [developer](), [documentation](), [http](), [migration](), [mozilla](), [security](), [web]() ### AI overview Mozilla announces that the HTTP Observatory has moved to MDN. The tool scans websites for security best-practice compliance, especially correct HTTP header usage, and provides scores, grades, actionable feedback, and documentation to help developers improve website security. ### Source excerpt First released in 2016, the HTTP Observatory became popular in the web community with a combination of helpful security audits and educational material. Fast forward to 2024, and we are delighted to announce that Observatory's new home is MDN. Read on to find out more about what this entails, and give the HTTP Observatory a warm welcome! ## onwebkitplaybacktargetavailabilitychanged?! New exotic events in the XSS cheat sheet DevFeed: [onwebkitplaybacktargetavailabilitychanged?! New exotic events in the XSS cheat sheet]() Original publisher: [Read original article]() Author: Gareth Heyes Published: 2024-06-11T14:58:29Z Content type: article Language: en Sources: [PortSwigger Research]() Topics: [Cheat sheet](), [Security](), [Web](), [Mozilla](), [marquee]() Tags: [audio](), [cheat-sheet](), [code](), [community](), [contribute](), [firefox](), [marquee](), [mozilla](), [security](), [tool](), [update](), [video](), [web]() ### AI overview An update to PortSwigger's XSS cheat sheet adds and documents exotic browser event vectors, including Safari audio and video behavior, pointer interaction, autofocus usage, and WebKit trackpad events. The article also credits community contributions and Mozilla's help removing obsolete marquee events from Firefox. ### Source excerpt The power of our XSS cheat sheet is we get fantastic contributions from the web security community and this update is no exception. We had valuable contributions from Mozilla to remove events that no ## Coming Soon: MDN Observatory 2.0 DevFeed: [Coming Soon: MDN Observatory 2.0]() Original publisher: [Read original article]() Author: mdn-team Published: 2023-10-25T00:00:00Z Content type: news Language: en Sources: [MDN Blog]() Topics: [Mozilla](), [Security](), [Website](), [User interface design](), [real-time]() Tags: [announcement](), [mozilla](), [real-time](), [security](), [updates](), [usability](), [web]() ### AI overview Mozilla announces MDN Observatory 2.0, an upcoming version of its website security analysis platform that will become part of the Mozilla Developer Network. It will introduce revised security scoring metrics, a redesigned interface, real-time analysis, and actionable recommendations. ### Source excerpt Observatory 2.0 is launching soon as part of the Mozilla Developer Network as the MDN Observatory with new security scoring standards and other exciting updates. ## Supabase Beta June 2023 DevFeed: [Supabase Beta June 2023]() Original publisher: [Read original article]() Author: Ant Wilson Published: 2023-07-06T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Artificial Intelligence](), [Authentication](), [Chat Bot](), [Command-line interface](), [database monitoring](), [Databases](), [Documentation](), [Google](), [Mozilla](), [OpenAI](), [Vue.js]() Tags: [ai](), [announcements](), [app](), [authentication](), [cli](), [database](), [database-monitoring](), [documentation](), [google](), [mozilla](), [openai](), [updates](), [vue]() ### AI overview Supabase's June 2023 beta update highlights its partnership with Mozilla on AI Help, a developer-documentation chatbot powered by Supabase Vector and OpenAI. It also announces native Google and Apple authentication, CLI improvements for migrations, Functions, and database monitoring, billing updates, Kakao login, realtime debugging tools, storage changes, and new documentation and community projects. ### Source excerpt A plethora of announcements... read till the end to find out when is the new Launch Week ## Leaving Mozilla DevFeed: [Leaving Mozilla]() Original publisher: [Read original article]() Published: 2021-02-10T18:23:05Z Content type: opinion Language: en Sources: [Emily Kager]() Topics: [Mozilla](), [Firefox](), [firefox for android](), [Mobile](), [Java]() Tags: [android](), [career](), [community](), [experience](), [firefox](), [firefox-for-android](), [growth](), [leadership](), [mozilla](), [oss](), [project](), [team](), [work](), [writing]() ### AI overview A personal account of joining Mozilla as an intern and working on Firefox for Android. The author describes finding a supportive team and meaningful work, then leaving to pursue something new after burnout from sustained workload around a major browser rewrite. ### Source excerpt I don't think any little girl grows up with the goal of "I want to be an OSS Android browser developer" and to be totally honest, even as an adult I just kind of fell into it. I first joined Mozilla as an intern during my change-career journey mainly because I had taken one Android class, knew some Java, and applied on a whim at the right time to hit the recruiter's inbox. Despite not actively seeking Mozilla or Android out, I immediately fell in love with the project and team and knew I had stumbled into a very special place. The problems were interesting, I had opportunities for leadership and growth from the start, and the people were kind, smart, and supportive. ## Live coding a browser in Kotlin DevFeed: [Live coding a browser in Kotlin]() Original publisher: [Read original article]() Published: 2019-12-17T17:25:49Z Content type: tutorial Language: en Sources: [Colin The Shots]() Topics: [browser](), [Kotlin](), [Android](), [Mozilla](), [Open Source](), [coding]() Tags: [android](), [browser](), [coding](), [kotlin](), [kotlinconf](), [learn](), [live](), [mozilla](), [open-source](), [uncategorized]() ### AI overview A video demonstrates live coding an Android web browser in Kotlin using Mozilla's open source Android Components and GeckoView engine. ### Source excerpt I recently live coded an Android web browser on stage at KotlinConf 2019 in Copenhagen. You can check it out and learn all about how to use Mozilla's open source Android Components and our GeckoView ## Digging into regressions DevFeed: [Digging into regressions]() Original publisher: [Read original article]() Author: elvis314 Published: 2019-08-23T20:53:47Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [bug](), [data](), [Mozilla](), [monitor](), [Web platform]() Tags: [bug](), [data](), [monitor](), [mozilla](), [platform](), [regression](), [testdev](), [tests](), [web]() ### AI overview The article examines how Mozilla tracks regressions detected by builds and tests after patches land on autoland. It proposes distinguishing unique regressions and product fixes, while considering data accuracy, backouts, and the potential impact of changing or disabling test jobs. ### Source excerpt Whenever a patch is landed on autoland, it will run many builds and tests to make sure there are no regressions. Unfortunately many times we find a regression and 99% of the time backout the changes so they can be ... Continue reading -> ## Colin Lee joins Mozilla as a Senior Android Engineer working on Firefox Android products DevFeed: [Colin Lee joins Mozilla as a Senior Android Engineer working on Firefox Android products]() Original publisher: [Read original article]() Published: 2018-07-30T19:22:10Z Content type: opinion Language: en Sources: [Colin The Shots]() Topics: [Mozilla](), [Firefox](), [Android](), [android-development](), [Kotlin](), [Open Source](), [Java]() Tags: [android](), [android-development](), [code](), [development](), [firefox](), [java](), [kotlin](), [mozilla](), [open-source](), [software](), [uncategorized]() ### AI overview Colin Lee announces that he has joined Mozilla as a Senior Android Engineer working on Firefox Android products. He plans to write about his open-source Android development work, initially using Kotlin in projects that include existing Java source. ### Source excerpt Colin Lee from ColinTheShots LLC just joined Mozilla as the newest Senior Android Engineer working on Firefox Android products. I'll be changing my professional consulting site to function as a blog. ## Firefox 57 CPU usage is insane DevFeed: [Firefox 57 CPU usage is insane]() Original publisher: [Read original article]() Author: Stanko Published: 2017-11-28T00:00:00Z Content type: opinion Language: en Sources: [Stanko Tadić]() Topics: [Firefox](), [browser](), [Mozilla](), [Extension](), [macOS]() Tags: [browser](), [extension](), [firefox](), [macos](), [mozilla](), [update]() ### AI overview A personal rant about Firefox 57 (Quantum) using excessive CPU and draining battery on macOS. The author switched to Opera because disabling extensions did not help, while later updates report that the issue was eventually fixed. ### Source excerpt This is a sad rant :( I love Firefox (and Mozilla too) and have never switched to ChromeAlthough I use Chrome for development. But few days ago I switched to Opera, because new Firefox's (aka Quantum) CPU usage is insane. Disabling extensions didn't help, it just hogs all available resources. MacOS is giving me "Service Battery" warning when Firefox is running. And battery last about four times(!) shorter. So I checked my options, and decided to go with Opera. One of my favorite features in Firefox, tabs on the side, is not supported in Chrome and Safari, so only decent browser left was Opera. Opera has Tree Tabs extension, which is not as good as Tree Style Tab but it is good enough. I'm getting used to it, and so far so good. Although I do hope Firefox will resolve CPU issues. If they haven't hyped it so much, I probably wouldn't be writing this. But they raised my expectations, how much faster and better it is, how they finally caught up... and it is bad, like really bad. I've tried both beta and developer editions some time ago, and fans were going crazy, CPU usage was going through the roof, battery drainage... But I hoped that it will get resolved before they release a stable version. I'm really sad, but if they don't fix this I won't be switching back to Firefox. Still, I'm going to continue supporting and donating to Mozilla. On the plus side, MDN is one of the best sites for web development resources. Update 02. Decemeber 2017 It seems that guys from Mozilla are aware of it and that they are trying to fix it. Hooray! Update 04. December 2018 Unfortunately, even today with version 63.0.3 issue doesn't seem to be resolved. I'm sticking with Opera, but I switched to Simple Vertical Tabs extension. Update 26. September 2019 It is fixed! ## A formal introduction to Ionut Goldan - Mozilla's new Performance Sheriff and Tool hacker DevFeed: [A formal introduction to Ionut Goldan - Mozilla's new Performance Sheriff and Tool hacker]() Original publisher: [Read original article]() Author: elvis314 Published: 2017-10-18T19:57:53Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Mozilla](), [toolchain](), [build times](), [Python](), [Front end](), [Material Design]() Tags: [build-times](), [community](), [contribution](), [developers](), [mozilla](), [performance](), [toolchain]() ### AI overview A Q&A introduces Ionut Goldan, Mozilla's performance sheriff and tool hacker. It describes his work handling Talos alerts and related performance data from Autophone, Build Metrics, AWSY, and platform microbenchmarks, followed by discussion of his background and earlier programming projects. ### Source excerpt About 8 months ago we started looking for a full time performance sheriff to help out with our growing number of alerts and needs for keeping the Talos toolchain relevant. We got really lucky and ended up finding Ionut (:igoldan ... Continue reading -> ## Test Ownership DevFeed: [Test Ownership]() Original publisher: [Read original article]() Author: gbrown-mozilla Published: 2017-06-08T04:17:33Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [bug](), [Code](), [Mozilla]() Tags: [bug](), [code](), [intermittent-failures](), [mozilla](), [project-stockwell](), [testing](), [tests]() ### AI overview The article examines who should be responsible for intermittent test failures. It considers assigning responsibility to the test author, the person who last modified the test, the person whose changeset caused the failure, or the module owner, and discusses the benefits and limitations of these approaches. ### Source excerpt When a bug for an intermittent test failure needs attention, who should be contacted? Who is responsible for fixing that ... Continue reading -> ## Marionette, Act II: Harnessing automation to test the browser DevFeed: [Marionette, Act II: Harnessing automation to test the browser]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-08-22T00:00:00Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [Browser Automation](), [Testing](), [Firefox](), [Mozilla](), [Python](), [API]() Tags: [api](), [automation](), [browser](), [firefox](), [marionette](), [mozilla](), [python](), [test]() ### AI overview This article explains the Marionette test harness, a testing framework for running automated tests on Mozilla browsers using the Marionette automation tools. It describes how browser automation supports testing instead of manual checks, with a Python API controlling the Gecko browser engine. ### Source excerpt Welcome back to my post series on the Marionette project! In Act I, we looked into Marionette's automation framework for Gecko, the engine behind the Firefox browser. Here in Act II, we'll take a look at a complementary side of the Marionette project: the testing framework that helps us run tests using our Marionette-animated browser, aka the Marionette test harness. If - like me at the start of my Outreachy internship - you're clueless about test harnesses, or the Marionette harness in particular, and want to fix that, you're in the right place! Wait, what's Marionette again? Quick recap from Act I: Marionette refers to a suite of tools for automated testing of Mozilla browsers. In that post, we saw how the Marionette automation framework lets us control the Gecko browser engine (our "puppet"), thanks to a server component built into Gecko (the puppet's "strings") and a client component (a "handle" for the puppeteer) that gives us a simple Python API to talk to the server and thus control the browser. But why do we need to automate the browser in the first place? What good does it do us? Well, one thing it's great for is testing. Indulge me in a brief return to my puppet metaphor from last time, won't you? If the automation side of Marionette gives us strings and a handle that turn the browser into our puppet, the testing side of Marionette gives that puppet a reason for being, by letting it perform: it sets up a stage for the puppet to dance on, tell it to carry out a given performance, write a review of that performance, and tear down the stage again. OK, OK, metaphor-indulgence over; let's get real. Wait, why do we need automated browser testing again? As Firefox1 contributors, we don't want to have to manually open up Firefox, click around, and check that everything works every time we change a line of code. We're developers, we're lazy! Clueless via POPSUGAR But we can't not do it, because then we might not realize that we've broken the entire internet (or, yo ## Outreachy Internship Update: Learning Mozilla's Development Process and Refactoring Marionette's Python Test Runner DevFeed: [Outreachy Internship Update: Learning Mozilla's Development Process and Refactoring Marionette's Python Test Runner]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-08-02T00:00:00Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [Development](), [Mozilla](), [Testing](), [Python](), [Refactoring](), [Test-driven development](), [Pytest](), [Firefox]() Tags: [development-process](), [firefox](), [internship](), [marionette](), [mozilla](), [mozreview](), [outreachy](), [pytest](), [python](), [refactoring](), [test](), [testing](), [treeherder]() ### AI overview An Outreachy intern reflects on the first part of an internship with Mozilla, describing the process of learning Mozilla's development tools and workflows. The article also outlines work on test-driven refactoring of Marionette's Python test runner and previews a follow-up post about its test runner and harness. ### Source excerpt It feels like yesterday that I started my Outreachy internship, but it was actually over 2 months ago! For the last couple of weeks I've been on Outreachy hiatus because of EuroPython, moving from Saarbrücken to Berlin, and my mentor being on vacation. Now I'm back, with 6 weeks left in my internship! So it seems like a good moment to check in and reflect on how things have been going so far, and what's in store for the rest of my time as an Outreachyee. What have I been up to? Learning how to do the work In the rather involved application process for Outreachy, I already had to spend quite a bit of time figuring out the process for making even the tiniest contribution to the Mozilla codebase. But obviously one can't learn everything there is to know about a project within a couple of weeks, so a good chunk of my Outreachy time so far was spent on getting better acquainted with: The tools I've already written about my learning experiences with Mercurial, but there were a lot of other components of the Mozilla development process that I had to learn about (and am still learning about), such as Bugzilla, MozReview, Treeherder, Try, Mach... Then, since the project I'm working focuses on testing, I had to grok things like Pytest and Mock. Since most everything I'm doing is in Python, I've also been picking up useful Python tidbits here and there. The project My internship project, "Test-driven refactoring of Marionette's Python test runner", relates to a component of the Marionette project, which encompasses a lot of moving parts. Even figuring out what Marionette is, what components it comprises, how these interrelate, and which of them I need to know about, was a non-trivial task. That's why I'm writing a couple of posts about the project itself - one down, one to go - to crystallize what I've learned and hopefully make it a little easier for other people to get through the what-even-is-it steps that I've been going through. This post is a sort of "intermission", so sta ## Understanding WebDriver, Selenium, Marionette, and Browser Automation DevFeed: [Understanding WebDriver, Selenium, Marionette, and Browser Automation]() Original publisher: [Read original article]() Author: Maja Frydrychowicz Published: 2016-07-12T04:00:00Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [webDriver](), [Browser Automation](), [Selenium](), [Testing](), [Firefox](), [HTTP](), [JSON](), [Mozilla](), [JavaScript](), [Open Source]() Tags: [automation](), [browser](), [browser-ui](), [browsers](), [client-driver](), [firefox](), [foss](), [geckodriver](), [harness](), [http](), [javascript](), [json](), [marionette](), [mozilla](), [open-source](), [payload](), [request](), [responses](), [selenium](), [w3c](), [web](), [webdriver]() ### AI overview An explanatory article untangles the terminology around Marionette, Selenium, WebDriver, FirefoxDriver, and geckodriver. It explains the W3C WebDriver Specification and how its browser-agnostic protocol uses JSON over HTTP to send commands and receive responses for browser automation and testing. ### Source excerpt I define WebDriver, W3C WebDriver, Selenium, geckodriver, FirefoxDriver, Marionette harness/runner/client/driver and more. ## adding "reviewer delegation" to MozReview DevFeed: [adding "reviewer delegation" to MozReview]() Original publisher: [Read original article]() Author: glob Published: 2016-07-04T07:20:06Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Code review](), [Extension](), [Authorization](), [Mozilla](), [Git]() Tags: [code-review](), [extension](), [mozilla](), [mozreview](), [permission](), [review]() ### AI overview This technical article describes the design challenges behind adding reviewer delegation to MozReview. It explains how MozReview integrates Review Board, Bugzilla, Mercurial, Git, and automation, and discusses permission handling, draft updates, and preserving the identity of the authenticated user when changes are attributed to the submitter. ### Source excerpt Background One of the first projects I worked on when I moved to the MozReview team was "review delegation". The goal was to add the ability for a reviewer to redirect a review request to someone else. It turned out to be a change that was much more complicated than expected. MozReview is a Mozilla [...] ## Mozilla London All Hands 2016 DevFeed: [Mozilla London All Hands 2016]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-06-20T00:00:00Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [Mozilla](), [Web]() Tags: [culture](), [event](), [executive](), [intern](), [london](), [mozilla](), [organization](), [outreachy](), [taskcluster](), [technology](), [web]() ### AI overview An Outreachy intern recounts attending Mozilla London All Hands 2016, highlighting the event's talks, meetings, team activities, and the opportunity to connect with Mozilla colleagues and interns. The article also reflects on finding valued female role models across Mozilla. ### Source excerpt Last week, all of Mozilla met in London for a whirlwind tour from TARDIS to TaskCluster, from BBC1 to e10s, from Regent Park to the release train, from Paddington to Positron. As an Outreachy intern, I felt incredibly lucky to be part of this event, which gave me a chance to get to know Mozilla, my team, and the other interns much better. It was a jam-packed work week of talks, meetings, team events, pubs, and parties, and it would be impossible to blog about all of the fun, fascinating, and foxy things I learned and did. But I can at least give you some of the highlights! Or, should I say, Who-lights? (Be warned, that is not the last pun you will encounter here today.) Foxy, the TARDIS, and espionage in the park? All in a day's work at #MozLondon! pic.twitter.com/QPWdPRnJHY -- Anjana Vakil (@AnjanaVakil) June 14, 2016 Role models While watching the plenary session that kicked off the week, it felt great to realize that of the 4 executives emerging from the TARDIS in the corner to take the stage (3 Mozillians and 1 guest star), a full 50% were women. As I had shared with my mentor (also a woman) before arriving in London, one of my goals for the week was to get inspired by finding some new role moz-els (ha!): Mozillians who I could aspire to be like one day, especially those of the female variety. Why a female role model, specifically? What does gender have to do with it? Well, to be a good role model for you, a person needs to not only have a life/career/lego-dragon you aspire to have one day, but also be someone who you can already identify with, and see yourself in, today. A role model serves as a bridge between the two. As I am a woman, and that is a fundamental part of my experience, a role model who shares that experience is that much easier for me to relate to. I wouldn't turn down a half-Irish-half-Indian American living in Germany, either. At any rate, in London I found no shortage of talented, experienced, and - perhaps most importantly - valued women at Mo ## Warming up to Mercurial DevFeed: [Warming up to Mercurial]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-06-03T00:00:00Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [Mercury](), [Git](), [Firefox](), [Mozilla](), [Testing]() Tags: [firefox](), [git](), [graph](), [install](), [marionette](), [mozilla](), [repo](), [testing](), [version-control]() ### AI overview A developer documents learning Mercurial after working primarily with Git, explaining basic repository operations and terminology while contributing to Mozilla's Marionette project for Firefox. The article highlights similarities between Mercurial and Git and describes differences involving logs, graphs, changesets, revisions, and identifiers. ### Source excerpt When it comes to version control, I'm a Git girl. I had to use Subversion a little bit for a project in grad school (not distributed == not so fun). But I had never touched Mercurial until I decided to contribute to Mozilla's Marionette, a testing tool for Firefox, for my Outreachy application. Mercurial is the main version control system for Firefox and Marionette development,1 so this gave me a great opportunity to start learning my way around the hg. Turns out it's really close to Git, though there are some subtle differences that can be a little tricky. This post documents the basics and the trip-ups I discovered. Although there's plenty of other info out there, I hope some of this might be helpful for others (especially other Gitters) using Mercurial or contributing to Mozilla code for the first time. Ready to heat things up? Let's do this! Getting my bearings on Planet Mercury OK, so I've been working through the Firefox Onramp to install Mercurial (via the bootstrap script) and clone the mozilla-central repository, i.e. the source code for Firefox. This is just like Git; all I have to do is: $ hg clone (Incidentally, I like to pronounce the hg command "hug", e.g. "hug clone". Warm fuzzies!) Cool, I've set foot on a new planet! ...But where am I? What's going on? Just like in Git, I can find out about the repo's history with hg log. Adding some flags make this even more readable: I like to --limit the number of changesets (change-whats? more on that later) displayed to a small number, and show the --graph to see how changes are related. For example: $ hg log --graph --limit 5 or, for short: $ hg log -Gl5 This outputs something like: @ changeset: 300339:e27fe24a746f |\ tag: tip | ~ fxtree: central | parent: 300125:718e392bad42 | parent: 300338:8b89d98ce322 | user: Carsten "Tomcat" Book | date: Fri Jun 03 12:00:06 2016 +0200 | summary: merge mozilla-inbound to mozilla-central a=merge | o changeset: 300338:8b89d98ce322 | user: Jean-Yves A ## Firefox-ui-tests - Platform Operations Project of the Month DevFeed: [Firefox-ui-tests - Platform Operations Project of the Month]() Original publisher: [Read original article]() Author: Admin Published: 2016-06-02T09:18:23Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Testing](), [ci](), [Puppeteer](), [Automation](), [Mozilla](), [Jenkins]() Tags: [automation](), [browser](), [ci](), [continuous-integration](), [firefox](), [jenkins](), [marionette](), [mozilla](), [mozmill](), [taskcluster](), [testing](), [tests](), [treeherder]() ### AI overview This article presents firefox-ui-tests as a Mozilla project for integration testing of Firefox's user interface. The tests use the Marionette automation framework and Firefox Puppeteer's page object model, run across Firefox code-check and release workflows, and include localized-build and update testing. The project's work includes improving result visibility, test placement, stability, and coverage. ### Source excerpt Hello from Platforms Operations! Once a month we highlight one of our projects to help the Mozilla community discover a useful tool or an interesting contribution opportunity. This month's project is firefox-ui-tests! What are firefox-ui-tests? Firefox UI tests are a test suite for integration tests which are based on the Marionette automation framework and are majorly used for user interface centric testing of Firefox. The difference to pure Marionette tests is, that Firefox UI tests are interacting with the chrome scope (browser interface) and not content scope (websites) by default.Continue readingFirefox-ui-tests - Platform Operations Project of the Month ## Review of Firefox desktop automation work - Q1 2016 DevFeed: [Review of Firefox desktop automation work - Q1 2016]() Original publisher: [Read original article]() Author: Admin Published: 2016-03-31T14:10:13Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Automation](), [Puppeteer](), [Mozilla](), [GitHub]() Tags: [automation](), [build-system](), [ci](), [debug](), [files](), [firefox](), [github](), [linux](), [marionette](), [mozilla](), [mozqa](), [qa](), [reports](), [testing](), [tests](), [ui]() ### AI overview A Q1 2016 review of Firefox desktop automation work describes Mozharness and Build System changes, a Firefox UI test task in Taskcluster, and the move of Firefox UI tests and their harness to mozilla-central. ### Source excerpt Today is the last day of Q1 2016 which means time to review what I have done during all those last weeks. When I checked my status reports it's kinda lot, so I will shorten it a bit and only talk about the really important changes. Build System / Mozharness After I had to dig into mozharness to get support for Firefox UI Tests during last quarter I have seen that more work had to be done to fully support tests which utilize Nightly or Release builds of Firefox. TheContinue readingReview of Firefox desktop automation work - Q1 2016 ## Write and deploy your own self-hosted Readability clone DevFeed: [Write and deploy your own self-hosted Readability clone]() Original publisher: [Read original article]() Published: 2016-03-29T00:00:00Z Content type: tutorial Language: en Sources: [Adam Bard]() Topics: [Self-hosted](), [Node.js](), [Library](), [Heroku](), [Software](), [Code](), [Document Object Model (DOM)](), [App](), [Mozilla](), [browser]() Tags: [app](), [browser](), [code](), [deploy](), [heroku](), [libraries](), [node-js](), [self-hosted](), [software]() ### AI overview A tutorial for building and deploying a self-hosted Readability clone with Heroku and Node.js. It uses Mozilla's Readability.js through readability-node, jsdom to provide a DOM, and a Node.js server to fetch URLs and display extracted article text. ### Source excerpt Readability.org is a handy tool, but it also suffers from being useful, popular and free - the service is (understandably) often down, or slow. If you're a heavy Readability user, it might interest you to know that there exist many software libraries that attempt to recreate Readability's main function - pulling the main body of text out of a page laden with ads and other distractions. Some of these work better than others, but Mozilla's Readability. [Next page]()