The release of web browser Firefox 159 has taken place along with updates for previous long-term support branches \u2014 153.6.0 and 115.44.0. As part of the new two-week release cycle, the Firefox 160 branch has entered beta-testing, with its release scheduled for November 10. <\/p>\n
Key new features in Firefox 159 (1, 2, 3):<\/p>\n
\n
A button for accessing saved passwords has been added to the sidebar by default.\n
<\/center><\/p>\n
The 'Smart Window' mode, which provides a separate interaction space with AI, has been enhanced with the ability to track changes on web pages. For example, this new feature allows users to monitor price drops on items in online stores. To enable tracking, use the command '\/watch' in the chat with the built-in AI assistant, and to manage it \u2014 the 'Tasks' button on the panel or the page about:smartwindowtasks. Upon detecting a change, Firefox will display a notification.\n
The AI page content summarization feature has been revamped to send not the page text to the AI provider, but a link to the page, resolving issues with incomplete page analysis.\n
New keyboard shortcuts have been added: Ctrl+Shift+A for searching among open tabs and Ctrl+Shift+F for navigating to the management of add-ons or themes. Keyboard combinations can be modified on the page about:keyboard.\n
In macOS builds, the platform's default interface for sharing information through other applications, such as AirDrop and Messages, has been utilized. It's now possible to send multiple selected tabs at once.\n
In the web developer tools, variable redefinitions previously declared with let, const, and class are now allowed in the web console.\n
Support for scroll-driven animations has been added, allowing the creation of indicators for visually representing page position or adding effects that change content when appearing in the viewport during scrolling. Two modes are available: 'ScrollTimeline' for binding to scroll position relative to the coordinate axis and 'ViewTimeline' for binding to the relative offset of individual content elements in the scrollable area. New CSS properties animation-timeline, scroll-timeline, view-timeline, and animation-range have been introduced.\n
Support for user-defined element registries has been implemented to separate the visibility of custom HTML elements, which may be necessary when using multiple different custom HTML elements with the same name on one page. When multiple libraries defining elements with the same name are used on a page, the CustomElementRegistry() JavaScript constructor can be utilized to attach elements from each library to specific parts of the DOM hierarchy that do not overlap with the global registry window.customElements. For example, if two libraries define different elements with the same name , the element from the first library can be used in one part of the page, while in another part, the one from the second library can be used.\n
The WebGL API has added support for the EXT_clip_control and EXT_texture_mirror_clamp_to_edge extensions, and in WebGL 2, the EXT_texture_norm16 extension.\n
In the Sanitizer API, HTML code has been cleaned at the parsing stage, before elements are added to the DOM tree, which resolved the issue with the constructors of user-defined elements being removed during this cleaning process.\n
In the Android version, the frequency of tab reloads on Xiaomi and Redmi devices has been significantly reduced. The issue with video playback on sites like The New York Times has been resolved.\n
In Firefox Enterprise, administrators are now able to request a re-login using a corporate account before restoring a session after a process crash. Data SBOM (Software Bill of Materials) generation has been provided for Firefox Enterprise builds. By default, the use of AI for form autofill has been disabled.\n<\/ul>\n
In addition to new features and bug fixes, Firefox 159 has addressed 167 vulnerabilities, 108 of which have been classified as high risk. Most of these vulnerabilities are due to memory management issues, such as buffer overflows and access to freed memory areas. Potentially, these issues can lead to the execution of malicious code when specially crafted pages are opened. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
![](\"\/wp-content\/uploads\/2026\/10\/0fd08ab48c6568ef1b6f84718a0e96d2.png\")
<\/center><\/p>\n