30 Sep 2026
Planet Mozilla
About:Community: A fresh Firefox and MozFest count down
Hi Mozillian,
In this edition, we're exploring the new Firefox design, Mozilla's recent partnership with Mistral to expand choice in AI-powered browsing, and several ways to get involved with MozFest. You can join a livestream about the value of bringing open-source communities together in person, volunteer at MozFest in Barcelona, or take part in the latest privacy discussion from the Firefox community on Reddit.
Read on for the latest updates and opportunities to participate!
More modern. More flexible. Still Firefox.
Firefox 157 introduces a new Firefox design with updated colors, icons and themes that make the browser feel more modern while preserving the familiar Firefox experience. The release also brings back Compact Mode and adds easier theme selection, new wallpapers and more ways to customize the New Tab page. Underneath the new look, Firefox remains independent and open source, with built-in privacy protections and controls that let you decide how your browser works, including how AI features appear.
Mozilla and Mistral partner to expand AI choice
Mozilla and Mistral have announced a partnership aimed at increasing competition and preserving user choice in AI-powered browsing. As part of the collaboration, the open-source Mistral Small 4 model is coming to Firefox Smart Window Beta as a new option for users in the US and Canada. Smart Window Beta is also expanding to France with official French-language support, with additional European markets planned. Users can continue choosing from multiple AI models, reinforcing Firefox's commitment to avoiding lock-in and keeping the web open to different technologies and providers.
Does open source need IRL? The case for MozFest
Is showing up in person important for open source? Join the Owners Not Renters livestream on Tuesday, September 29, to hear the story behind MozFest and explore why gathering in person still matters for open-source communities ahead of MozFest, taking place October 28-30 in Barcelona. Kali Villarosa (MoFo), Seher Shafiq (MoFo) and Brian Behlendorf (co-founded Apache) will join host Marcus Rein for an open conversation, followed by a live Q&A. Bring your questions and your hot takes!
MozFest call for Volunteers
From 28-30 October 2026, the Mozilla Foundation will host the Mozilla Festival in Barcelona, bringing together people from diverse fields to explore how we can work collectively to "re-wild" the web. To help bring the Festival to life, we're building a team of volunteers. By joining, you'll help deliver a major event in support of Mozilla's mission while also having opportunities to participate in sessions throughout the three-day Festival.
From the Reddit Community
Privacy conversations are going mainstream, and Firefox has been at this for 20+ years. In light of a recent video making the rounds about the importance of privacy, the Firefox Team shared a rundown of built-in privacy features (ad blocking, tracking protection, encrypted sync, a free VPN, and more). Jump in at r/firefox and share your own privacy tips and configs!
P.S.
Enjoyed these updates? Subscribe to the Mozilla Community Newsletter and get the latest updates delivered straight to your inbox.
30 Sep 2026 5:01pm GMT
This Week In Rust: This Week in Rust 671
Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @thisweekinrust.bsky.social on Bluesky or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.
This Week in Rust is openly developed on GitHub and archives can be viewed at this-week-in-rust.org. If you find any errors in this week's issue, please submit a PR.
Want TWIR in your inbox? Subscribe here.
Updates from Rust Community
Newsletters
Observations/Thoughts
- Can safe Rust ever beat Google's C Brotli?
- Building a DMA based driver for the RP2350 I2C (safety not included)
- Advanced soft-bodies for games with the Rapier physics engine
- Supporting native Rust in Workers with the new Emscripten target for wasm-bindgen
- Rusty thoughts on "Parse, don't validate"
- The state of SIMD in Rust in 2026
- How do you stop being a Rust novice?
- We Have Named Arguments at Home: a reply to the blog post Arguing about arguments mentioned in the last issue
- Upstream Rust maintenance report (August-September 2026)
- Rust in the kernel? What about Rust without the kernel!
- Compiling the kernel with gccrs
- Listening to the radio with Rust
- Native support for Rust on the GPU
Rust Walkthroughs
- How to speed up the Rust compiler in September 2026
- Building Real-Time Notifications with SSE and Pub/Sub
- Green Threads from Scratch
- A Type Stronger than the Sum of its Components
- Deser: Rethinking Rust Serialization
- Dropping Swift from our Bevy iOS crates
- Pining for Arc Downcasting in Rust
- Topcoat is pushing the boundary of server applications with Rust
- Rust Reborrowing, Aliasing, and Mutable References
- A very condensed introduction of the basics of Rust
- [video] Making Our GPUI App Interactive with State and Events
- [ES] Domain-Flow-Effects (DFE): an architecture designed for Rust
Miscellaneous
Crate of the Week
This week's crate is ying-profiler, a native Rust sampling memory profiler.
Thanks to Evan Chan for the self-suggestion!
Please submit your suggestions and votes for next week!
Calls for Testing
An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization.
If you are a feature implementer and would like your RFC to appear in this list, add a call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.
No calls for testing were issued this week by Rust, Cargo, Rustup or Rust language RFCs.
Let us know if you would like your feature to be tracked as a part of this list.
Call for Participation; projects and speakers
CFP - Projects
Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!
Some of these tasks may also have mentors available, visit the task page for more information.
- unsynced - strace frontend fails on pwritev2 with offset -1 (current file offset)
- unsynced - Model hard links (link/linkat) instead of warning
- unsynced - Add an ext4 data=writeback persistence profile
- MemoryWhale - Cover friendly errors for incomplete
mwarguments - MemoryWhale - Lock down
mw --helpoutput - dataprof - Remote Parquet refusal messages should say to download the file when the server ignores Range
- dataprof -
ScoreBounds::dimension_scoresdocs still list estimated key counts as unbounded - dataprof - The progress
finishedevent under-counts rows when a row cap stops the incremental engine
If you are a Rust project owner and are looking for contributors, please submit tasks here or through a PR to TWiR or by reaching out on Bluesky or Mastodon!
CFP - Events
Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.
If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a PR to TWiR or by reaching out on Bluesky or Mastodon!
Updates from the Rust Project
546 pull requests were merged in the last week
Compiler
- computing
crate_hashfrom metadata encoding instead of HIR (implements #94878) - detect missing else in let statement
- give noalias back to refs in closures
- implement forced keywords (
k#) - use SmallVec in LocalizedConstraintGraph
Library
- add
DivandMulforComplex<{float}> - alloc: stabilise
Allocator - additional
NonZeroconversions - allow elided (
'static) lifetimes inthread_local! - implement
PartialEq<VecDeque<U>>forVec<T>,&[T],&mut [T],[T; N],&[T; N]and&mut [T; N] - make dropping an empty BTreeMap free
- stabilize SyncView
- stabilize
Box::take - stabilize
Result::into_{ok,err} - stabilize
funnel_shifts(includingconst) - stabilize
mem::conjure_zst - stabilize
vec_try_remove - use wrapping arithmetic in
from_str_radix
Cargo
builtin-deps: add builtin dependencies manifest syntaxconfig: add build.profile, install.profilemetadata: mirror package features infeatures_v2builtin-deps: fix builtin dependencies manifest validationdiag: Don't report unused normal deps when static libs are skippedpackage: preserve feature metadata in normalized manifests
Rustdoc
- correctly check that an item is not
doc(hidden)with--generate-link-to-definition - fix intra doc link resolution when a doc comment is composed of both inner and outer doc comment
- fix invalid jump to def link when
#[rustc_allow_incoherent_impl]is involved - fix quadratic naming of duplicate sidebar links
Clippy
while_let_loop: detect the pattern when the loop has a label- add new
try_from_instead_of_from_strlint - don't suggest
Box::leakinnonnull_unchecked_on_box_ptr - fix
collapsible_matchconsuming/mutation checking - fix
match_str_casematching str inside or patterns - improve doc attr span tracking for proc-macro
Rust-Analyzer
- don't fail extension activation when the server fails to start
- add
type_matchrelevance for type-alias - coercion safe fn to unsafe fn
- complete 'false' in cfg attribute
- complete attr value inside string without quotes
- const eval cast of single-variant
enum - deduplicate 'derive' and 'test' attribute macro
- do not type match unknown type
- don't clear semantic tokens cache on refresh
- hover show impl header when impl with trait
- panic in async closures with higher-ranked trait bounds
- return UB instead of panicking when reading the discriminant of an uninhabited
enum
Rust Compiler Performance Triage
This week was fairly positive. We had no pure regressions, and most of the results came from a few architectural improvements with mixed or mostly positive impact. Some improvements also come from addressing previously triaged regression caused by missing no_alias annotation for references in closures.
The biggest improvement this week is in rustdoc, from tackling quadratic behaviour when generating sidebar links. This was reported by a user, but the effect didn't show up in our benchmarks, so we added a special stress test for it.
Triage done by @panstromek. Revision range: 3670d253..c1070d69
Summary:
| (instructions:u) | mean | range | count |
|---|---|---|---|
| Regressions ❌ (primary) |
0.6% | [0.2%, 0.8%] | 8 |
| Regressions ❌ (secondary) |
1.4% | [0.1%, 5.8%] | 30 |
| Improvements ✅ (primary) |
-0.6% | [-1.7%, -0.2%] | 192 |
| Improvements ✅ (secondary) |
-1.5% | [-82.5%, -0.1%] | 101 |
| All ❌✅ (primary) | -0.6% | [-1.7%, 0.8%] | 200 |
0 Regressions, 2 Improvements, 6 Mixed; 3 of them in rollups 26 artifact comparisons made in total
Approved RFCs
Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:
- No RFCs were approved this week.
Final Comment Period
Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.
Tracking Issues & PRs
- Stop using dlltool for generating import libraries on MinGW
- Stabilize
ptr::try_cast_aligned - [disposition: close] 1.99 beta crater regression: overflow evaluating the requirement
- implement FCW for
rustc_allowed_through_unstable_modulesitems - fix
VisibleForLeakCheckinRegionOutlivesfast path - Stabilize
debug_closure_helpers - Support type-relative assoc item paths in generic param defaults & const param types
- FCW for
#[panic_handler]onunsafe fn. - Stabilize
optimizeattribute - Allow unary operand types to be inferred later
- Feat -
#[inline(always)] + #[target_feature(enable = "....")]#2 - Tracking Issue for
CStr::display - Syntactically reject leading parenthesized precise capturing lists in bare trait object types (
(use<…>)+)
No Items entered Final Comment Period this week for Language Team, Language Reference, Leadership Council or Unsafe Code Guidelines. Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
New and Updated RFCs
Upcoming Events
Rusty Events between 2026-09-30 - 2026-10-28 🦀
Virtual
- 2026-09-30 | Virtual (Cardiff, UK) | Rust and C++ Cardiff
- 2026-10-01 | Virtual | Rust Foundation & JetBrains
- 2026-10-02 | Virtual | Rust Girona
- 2026-10-03 | Virtual (Amsterdam, NL) | Bevy Game Development
- 2026-10-04 | Virtual (Dallas, TX, US) | Dallas Rust User Meetup
- 2026-10-06 | Virtual (London, UK) | Women in Rust
- 2026-10-07 | Virtual (Indianapolis, IN, US) | Indy Rust
- 2026-10-08 | Virtual (Berlin, DE) | Rust Berlin
- 2026-10-08 | Virtual (Nürnberg, DE) | Rust Nuremberg
- 2026-10-10 | Virtual (Gdansk, PL) | Stacja IT Trójmiasto
- 2026-10-10 | Hybrid (Kuala Lumpur, Malaysia) | Rust Malaysia Meetup
- 2026-10-13 | Virtual (Dallas, TX, US) | Dallas Rust User Meetup
- 2026-10-14 - 2026-10-17 | Hybrid (Barcelona, ES) | EuroRust
- 2026-10-18 | Virtual (Dallas, TX, US) | Dallas Rust User Meetup
- 2026-10-20 | Virtual (Washington, DC, US) | Rust DC
- 2026-10-21 | Hybrid (Vancouver, CA) | Vancouver Rust
- 2026-10-22 | Virtual (Berlin, DE) | Rust Berlin
- 2026-10-27 | Virtual (Dallas, TX, US) | Dallas Rust User Meetup
- 2026-10-27 | Virtual (London, UK) | Women in Rust
Asia
- 2026-10-09 | Hybrid (Kuala Lumpur, MY) | Rust Malaysia Meetup
Europe
- 2026-09-30 | Basel, CH | Rust Basel
- 2026-09-30 | Berlin, DE | Rust Berlin
- 2026-10-01 | Berlin, DE | Rust Berlin
- 2026-10-01 | Oxford, GB | Oxford ACCU/Rust Meetup.
- 2026-10-05 | München, DE | Rust Munich
- 2026-10-08 | Oslo, NO | Rust Oslo
- 2026-10-08 | Geneva, CH | Rust Geneva
- 2026-10-14 | Barcelona, ES | BcnRust
- 2026-10-14 - 2026-10-17 | Hybrid (Barcelona, ES) | EuroRust
- 2026-10-20 | Leipzig, DE | Rust - Modern Systems Programming in Leipzig
North America
- 2026-10-01 | Saint Louis, MO, US | STL Rust
- 2026-10-03 | Boston, MA, US | Boston Rust Meetup
- 2026-10-08 | Lehi, UT, US | Utah Rust
- 2026-10-08 | New York, NY, US | Rust NYC
- 2026-10-08 | San Diego, CA, US | San Diego Rust
- 2026-10-10 | Boston, MA, US | Boston Rust Meetup
- 2026-10-14 | Los Angeles, CA, US | Rust Los Angeles
- 2026-10-20 | San Francisco, CA, US | San Francisco Rust Study Group
- 2026-10-21 | Hybrid (Vancouver, CA) | Vancouver Rust
- 2026-10-21 | San Francisco, CA, US | Bay Area Rust
- 2026-10-28 | Austin, TX, US | Rust ATX
South America
- 2026-10-08 | Buenos Aires, AR | Rust en Español
If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.
Jobs
Please see the latest Who's Hiring thread on r/rust
Quote of the Week
The community is obnoxiously helpful. I asked a simple question on the Rust community Discord server. What is the best way to read a file in Rust? I expected a straightforward response. Instead, I got back a 2,000-word essay on the inner workings of IO, buffering, error handling, and ownership, plus links to four different blog posts and three different approaches depending on file size, and a working code example.
...
The Rust community has weaponized education against me. I'm now a better engineer than I was yesterday against my will.
Thanks to MusicalNinjaDad for the suggestion!
Please submit quotes and vote for next week!
This Week in Rust is edited by:
- nellshamrell
- llogiq
- ericseppanen
- extrawurst
- U007D
- mariannegoldin
- bdillo
- opeolluwa
- bnchi
- KannanPalani57
- tzilist
Email list hosting is sponsored by The Rust Foundation
30 Sep 2026 4:00am GMT
29 Sep 2026
Planet Mozilla
Mozilla Addons Blog: Nova is here: what changes for your Firefox theme
On September 29, Firefox 157 shipped Nova, the biggest refresh of the Firefox interface since Proton back in 2021. The browser frame is cleaner, the sidebar plays a bigger role, and vertical tabs are a first-class layout. Your theme continues to load, and most color and image properties work as they did before.
What does change is where those colors and images display, how some of them look next to each other, and a handful of properties that no longer have a visible effect. Most themes will look fine. Some, especially themes built around a background image, look different enough that you will want to take a look.
This post walks through what changed compared with the Proton interface, what to check in your theme, and what is still being worked on. If you only have five minutes, jump to the checklist.
What changed in the browser frame
The toolbar and sidebar now sit flush with the window edges, with no gaps between them.
For your theme, this means your frame color and background image have less empty space around them, and the edges where the toolbar, sidebar, and page meet are more visible.
| Area | Proton | Nova (Firefox 157) |
|---|---|---|
| Toolbar and sidebar | Flush with the window, no gaps or floating borders | Same as before |
| Horizontal tabs | Theme background applied to the tab strip | Same as before |
| Vertical tabs | Tab bar color on the tab strip | Tab bar color also shows on the toolbar |
| Sidebar | Separate panel | Shares the theme background with the toolbar area |
colors, accents and tabs
Accent color. The default Firefox theme uses Nova's purple accent. Every other theme, including yours, uses the operating system's accent color for buttons and other accented controls. Themes cannot set the accent color through the manifest, and is why your theme cannot show the purple you see in the default theme.
Focus and link colors. Firefox still applies its own blue and cyan to focus rings and some links when a theme other than the default is active.
The selected tab. Proton always drew a shadow under the selected tab, which helped it stand out even when a theme did not style it. Nova removes that shadow. If your theme relies on it, the selected tab can blend into the tab strip. Set the selected tab colors, with tab_selected and tab_line, so the selected tab stands out.
Button hover colors. Your button_background_hover and button_background_active colors also apply to buttons on the tab strip, and for buttons that sit on your frame background with vertical tabs. A solid color picked to match the toolbar can almost disappear there. Semi-transparent colors, for example rgba(0, 0, 0, 0.15) for hover and rgba(0, 0, 0, 0.3) for pressed, work on both backgrounds.
Sidebar and vertical tabs
- The sidebar shares your background. The theme background now continues under the sidebar, so the sidebar and the toolbar area appear as one surface.
- Set sidebar colors explicitly. Use
sidebarandsidebar_textfor sidebar panels. If you leave them out, Firefox picks colors for you, relevant to your theme's color. sidebar_borderis now a separator. The sidebar splitter is gone; the property now colors the line between the sidebar and the page.- Sidebar buttons follow your text color. Buttons and icons in the sidebar are derived from your text color rather than your toolbar button colors, so they can look slightly different from the toolbar.
- Vertical tabs and the toolbar. With vertical tabs, your tab bar color is also applied to the toolbar. If those two colors were chosen to contrast, check how they look together.
- Expand on hover. In Firefox 157, a sidebar that expands on hover may not show your theme's background. This is fixed in Firefox 158.
Properties that changed or no longer work
Some theme properties behave differently in Nova. Your theme still loads if it uses them; they just have no visible effect, or style something different.
| Property | In Nova |
|---|---|
ntp_text |
No longer styles the new tab page search box |
popup_text |
No longer styles the address bar dropdown; other popups still use it |
sidebar_highlight |
No visible effect; the default highlight color is used |
sidebar_highlight_text |
No visible effect |
toolbar_bottom_separator |
Acts as a separator next to or below the toolbar and around the page |
The theme manifest reference on MDN is being updated with these changes.
Themes with background images
Themes using images are where you are most likely to see a difference. Your image can now show behind the sidebar and vertical tabs, and an image designed for a wide, short toolbar rarely looks good stretched or tiled down a vertical panel. In our testing of popular themes, the image themes that look off in the sidebar mostly did before Nova too. We did test a number of themes but we invite you to do your own testing. Nova makes the sidebar more visible, so the issues are easier to notice.
You can now choose where your images go with the backgrounds_area property, available from Firefox 156:
- "auto" (the default): Firefox decides from
additional_backgrounds_alignment. If any image is aligned to the vertical center or bottom, images stay in the top toolbars; otherwise they cover the whole window. - "window": images cover the whole window, including behind the sidebar and vertical tabs.
- "top_toolbars": images stay in the toolbars at the top of the window, and the sidebar uses your frame color.
If your image was made for the toolbar only, "top_toolbars" with a frame color that suits the image is usually the quickest fix.
Also set a toolbar color, even a semi-transparent one. Without it, notification bars that appear above the page sit directly on your image and can be hard to read.
New Gradient Support
Nova's color themes use gradients, and you can too. The Nova theme manifests are the best working example; look at how they set colors for each surface, including the sidebar. backgrounds_area applies to gradients the same way it applies to images. Older versions of Firefox ignore color properties they don't recognize, so your theme still loads there; if you use a feature older versions reject, set strict_min_version in your manifest.
Checklist: what to check in your theme
Install your theme in Firefox 157 and look at it in each of these states:
- Horizontal tabs and vertical tabs.
- Sidebar closed, open, and expanded on hover. Also toggle "Customize sidebar" while the sidebar is open or expanded.
- Compact density, if your users are likely to use it (under settings -> appearance density(.
- A private window.
- Light and dark system settings, since the accent follows the operating system.
- Hover over the buttons on the tab strip.
Then, if something looks off:
- Set
tab_selectedandtab_lineso the selected tab stands out without Firefox's old shadow. - Set
sidebarandsidebar_textto colors that match your theme. - Use semi-transparent
button_background_hoverandbutton_background_activecolors. - Check that your tab bar and toolbar colors work together with vertical tabs enabled.
- For image themes, choose a
backgrounds_areaand set a toolbar color. - Remove or ignore properties that no longer have an effect.
- Publish an update on AMO so your users get the changes.
What we are still working on
Nova will evolve after launch. Firefox 158 ships on October 13 with the expand-on-hover sidebar fix. We are also working on these, with no release date yet:
- Focus and link colors that fit your theme instead of the fixed blue and cyan.
- A
popup_iconscolor for icons in menus and panels, separate from toolbar icons. - Theme colors for hover and selected states inside sidebar panels.
- Better hover states for tab strip buttons.
We will post again when these land.
For users who prefer the old look
Some of your users may miss Proton. From September 29, Mozilla is featuring a Firefox Proton theme in the Add-ons Manager for anyone who wants the previous look. It is a normal theme, so users can switch between it and yours at any time.
Resources
- Theme manifest reference on MDN: every color, image, and property, including
backgrounds_area. - Static themes on Extension Workshop : updated for Nova.
- Nova theme manifests: worked examples for gradients and sidebar colors; the themes themselves are on AMO, for example Nova Sun.
Questions?
We want your theme to look its best in Nova. If something looks wrong and the checklist does not fix it, tell us on Discourse and include a link to your theme and a screenshot. Those reports help us find the cases that need a Firefox fix rather than a theme change.
Thank you for making Firefox look like you and like your users.
The post Nova is here: what changes for your Firefox theme appeared first on Mozilla Add-ons Community Blog.
29 Sep 2026 3:34pm GMT

