Answer in brief
Firefox 157 arrived on September 29 with a new design and a warning when encryption keys are being recorded. The update makes a sensitive local configuration more visible, alongside everyday interface changes.
A browser update with two different kinds of visibility
Firefox 157 reached the release channel on September 29, 2026. Mozilla’s redesign changes the browser surfaces people use throughout the day, while a new Firefox encryption warning reveals a sensitive configuration that could otherwise be easy to overlook. The two changes belong in the same release, but they answer different questions: how the browser feels to use, and what is happening to the keys protecting a connection.
For an ordinary reader, the useful starting point is to separate appearance from security state. A different toolbar is immediately apparent; a setting that exposes encryption material may not be. Making that state visible creates an opportunity to investigate it. It does not tell the user who configured the device, why the setting exists, or whether any information has already been accessed.
What the key-recording warning actually reports
The release notes place the warning in the site information panel, reached through the shield icon, and in Settings. It appears when Firefox has been configured to record its encryption keys. Mozilla says that this could allow other software on the computer to read encrypted web traffic. The statement describes a condition on the computer, rather than announcing that every encrypted connection is newly vulnerable.
The sensible response depends on who manages the machine. On a work device, the relevant question is whether the configuration is intentional and authorized; on a personal computer, an unexpected change needs an explanation. A screenshot of the warning alone cannot identify its origin. Our interpretation is that the feature improves the browser’s ability to communicate a local risk without resolving the underlying investigation.
Compact mode gives screen space back to the page
Mozilla’s separate design announcement describes revised colors, icons and themes, a more accessible theme picker, and the return of compact mode. Reducing tab and toolbar spacing can be useful when a browser shares a small display with another application. It changes the amount of room occupied by browser controls, not the amount of information a website contains or its own navigation design.
That distinction helps users evaluate the refresh on their own terms. A comfortable layout for reading may differ from one for switching among many tabs. Trying the density and theme controls with a familiar workflow is more informative than judging a promotional screenshot. Mozilla describes the design as avoiding a performance cost, but this article does not supply an independent measurement of that claim.
The sidebar fallback has a functional trade-off
The updated sidebar is now enabled for everyone. Mozilla still documents a way to restore its predecessor by setting sidebar.revamp to false in about:config, and says that preference remains available through the end of 2027. The same change turns off vertical tabs. A user preserving a familiar panel therefore also gives up a newer way of arranging open pages.
For support teams, this is a reason to document the chosen layout together with the browser version. Two people on the same release can have different tab arrangements because of a preference. Instructions that merely say to open the sidebar may become confusing. A short explanation of the relevant setting can prevent a cosmetic troubleshooting exercise from silently changing how somebody organizes work.
Video improvements remain dependent on the device
Firefox 157 allows WebRTC calls to use hardware AV1 decoding where the device supports it. Hardware availability is an explicit boundary: installing the browser does not add a decoder to an incompatible machine. The release also lists fixes for rotated phone or tablet video in calls and for several playback and display problems. Those are specific corrections rather than evidence that all calls will improve equally.
A useful evaluation would keep the calling service, device and network conditions consistent and identify whether AV1 is actually in use. Without those details, an apparent improvement might have a different cause. The table separates the release’s visible controls from features with prerequisites, so readers can identify what they can change directly and what still depends on their environment.
| Change | Available behavior | Boundary |
|---|---|---|
| Key recording | Warning in site information and Settings | Reports configured recording; does not prove an attack |
| Compact mode | Reduced tab and toolbar spacing | Layout choice, not website redesign |
| Legacy sidebar | Temporary preference through end of 2027 | Disables vertical tabs |
| AV1 in WebRTC | Hardware decoding can be used | Requires a compatible device |
Security maintenance deserves its own line in the update
Mozilla’s advisory 2026-97, also dated September 29, lists vulnerabilities fixed in Firefox 157 and assigns the advisory a high impact level. It is a separate source from the interface announcement. The existence of the key-recording warning should not obscure those fixes, and the advisory should not be treated as proof that the warning itself detects one of the listed attacks.
The editorial lesson from this release is practical: evaluate a browser update as a collection of changes with different evidence. Design can be assessed through daily use, compatibility through the actual device, and security maintenance through the vendor’s advisory. A more explicit warning is valuable precisely because it starts a specific question about configuration, rather than offering a blanket promise of privacy.
Questions and answers
Does the warning mean a website has been hacked?
No. It reports a local browser configuration that records encryption keys. That configuration could allow other software on the computer to read encrypted traffic. Establishing why it was enabled requires checking the device and its management settings.
Can the previous sidebar still be restored?
Mozilla documents a temporary option: setting sidebar.revamp to false in about:config. It also disables vertical tabs, and Mozilla says the preference will remain available until the end of 2027.
Will every video call become faster?
The release enables hardware AV1 decoding for WebRTC only on devices that support it. It supplies no universal speed or battery improvement. Call software, the codec in use and the device all affect the outcome.