Important Browser Changes This Month: What SMEs Should Review

Based on the official announcements reviewed through August 24, 2026, this month’s changes are operational: browser extensions, release cycles for some browsers, and specific web behavior. They are especially relevant to teams managing company devices or maintaining internal web applications. This article does not claim to rank every browser development worldwide. It brings together documented items that small and medium-sized enterprises can review.

1. Chrome extensions: a key Manifest V2 date

Google says that all remaining Manifest V2 extensions will be removed from the Chrome Web Store on August 31, 2026. Source: Google’s official Chrome Manifest V2 deprecation timeline

There is an important device-level distinction. Manifest V2 extensions will cease to function for users upgrading to Chrome 139 and later. Installations on Chrome 138 or earlier may remain installed, but they will not receive updates and cannot be reinstalled from the Chrome Web Store after removal. Source: Google’s official Chrome Manifest V2 deprecation timeline

The practical editorial recommendation here is to export an inventory of installed extensions, link each one to a user, team, or workflow, and check for a replacement that supports Manifest V3. This is an audit suggestion, not a claim that every Manifest V2 extension will fail on every device at the same time.

• Review ad blockers, password managers, and VPN extensions.
• Include workflow add-ons as an audit suggestion where the company depends on them.
• Identify extensions with broad permissions or connections to internal systems.
• Test replacements before August 31 and keep a rollback plan if a replacement affects work.

2. Edge: the consumer move to Manifest V3

Microsoft Edge began its consumer transition away from Manifest V2 in August 2026. Completion is planned by the end of 2026, while enterprise deprecation is planned for early 2027, according to Microsoft’s announcement. Source: Microsoft’s announcement on moving the Edge extensions ecosystem to Manifest V3

The Chrome and Edge timelines should therefore be recorded separately in a company plan. An editorial recommendation is to track the browser, version, device type, extension status, and business owner instead of keeping only a general list of extension names. Consumer use and extensions managed by enterprise policy may need separate review; this article does not assume that the same response applies to both.

3. Faster release cycles mean more regular testing

Microsoft Edge is moving to a two-week major-release cycle starting with Edge 152, scheduled for stable release on August 27, 2026. Extended Stable remains on an eight-week cycle. Source: Microsoft’s announcement on the new Edge release cycle

Firefox will begin its two-week release cadence with Firefox 155 on September 1, 2026. Source: Mozilla’s announcement on the new Firefox release cadence For development teams, the editorial recommendation is to make compatibility testing a regular release step rather than an occasional project. Start with the login, file-upload, printing, payment, and identity integrations that the company actually uses.

A suggested test is to run internal finance or human-resources systems after a browser update and record the browser version, operating system, and tested function. If a problem appears, classify its impact and reproduce it before attributing the cause to a release cycle. That is a proposed working method, not evidence that an update caused any particular problem.

4. Firefox 154: features and security context

Firefox 154 was released on August 18, 2026. It added Local Network Access permission prompts for WebSocket connections and Smart Window suggestions for related tab groups. Source: the official Firefox 154 release notes Smart Window is being rolled out gradually, so it may not appear for all users immediately. Source: the official Firefox 154 release notes

Firefox 154 also fixed multiple high-impact security vulnerabilities, including sandbox escape, site-isolation, privilege-escalation, and use-after-free issues. Source: Mozilla’s official Firefox 154 security advisory This does not mean that every organization will experience the same impact. It does support an operational recommendation: review the Firefox update policy, test the release on a small group if internal applications are sensitive, and expand deployment according to the organization’s normal process.

5. Edge is changing unload behavior

In Edge 152 and 153, unload handlers will not run by default for 60% of page loads unless the site enables the event through Permissions Policy. The percentage rises to 80% in Edge 154 and 100% in Edge 155. Source: Microsoft Edge Beta Channel release notes

Web teams should treat reliance on unload as an item to inspect. This article does not establish that removing the dependency will improve performance or prevent data loss. The editorial recommendation is to search the codebase for unload, identify whether it is used to save state, send information, or close a session, and test alternatives in a non-production environment. Record the result for each Edge version instead of assuming one behavior everywhere.

A short SME action list

1. Create an extension inventory with the browser, version, owner, and business use.
2. Identify Manifest V2 dependencies and test replacements before August 31, 2026, for Chrome.
3. Test internal finance or human-resources systems on the browser versions supported by the company.
4. Inspect websites and applications for unload usage and record results from Edge 152 onward.
5. Deploy browser updates through managed deployment or a verification process appropriate to the environment.

The practical conclusion is that this month calls for an audit of dependencies rather than an assumed visual redesign. Focus on what the company actually uses, record the version and result, and distinguish documented information from assumptions that still need testing.