Back to articles

Extension Pulse, week of November 9: Chrome 157 and Firefox 160 are live, and AMO has a new agreement to accept

Chrome 157's four extension changes are live in stable, Firefox 160 shipped November 10, and AMO's enterprise channel opens December 1 with a new agreement.

Maxim Kosterin
15 min read
A loose orange watercolor brush loop rests on an empty hairline signature line, with three small calendar dots in the far corner, the last one tinted orange.
A loose orange watercolor brush loop rests on an empty hairline signature line, with three small calendar dots in the far corner, the last one tinted orange.

If you meant to audit your extension against Chrome 157 "before it hits stable" — that moment passed on November 3. Chrome 157 reached the stable channel exactly on its scheduled date, and the four changes it carries for existing extensions are now production behavior, rolling out to every Chrome user whether you tested them or not.

Chrome 157 is live: the audit window closed on November 3

157.0.8103.38/.39 landed on Windows and Mac on November 3, Linux and Android got .38 and iOS 157.0.8103.37 the same day, per Chromium Dash — no slip against the milestone schedule. Which means the changes W42 detailed and W45 last-called are no longer beta-channel trivia. Four of them reach existing extensions without a single line of code changing on your side, and three of the four fail silently:

  • publicSuffix rejects leading-dot hostnames. ".example.com"-style input — the shape cookie domains arrive in — now errors instead of getting a best-effort answer (CL 8464103).
  • alarms.clearAll() resolves to undefined, not a boolean (CL 8182627, with a compatibility kill-switch). Every if (await browser.alarms.clearAll()) branch just became dead code in production. The alarms deep dive is the place to re-audit your scheduling logic.
  • webRequest and DNR no longer see navigations started from sites the user put under "block all extensions" (CL 8497010). No error is raised; the events simply never arrive, and permission-less block rules stop matching too. "No event" no longer means "no navigation".
  • X-Chrome-Manage-Accounts is hidden from extensions on Gaia URLs (CL 8501321). You can't read, modify or inject it on accounts.google.com anymore, and no extension API replaces it.

The milestone's fifth change is documentation-only: the MV2 browser_action / page_action contextMenus types are marked nodoc — out of the docs, still validating (CL 8507256).

If you ran the W45 audit, none of this is new — go ship something else. If you didn't: you are testing in production now. The four greps take ten minutes, and they're in What I'd do this week below.

And the release train isn't slowing down. Chrome 158 started its own early-stable rollout on November 4 — one day after 157's stable date — putting 158.0.8127.18 on Windows and Mac and .22 on Android thirteen days ahead of its full stable on November 17 (Dash). That's the same rhythm M155 and M156 set. The silver lining: 158 is a breather. Its beta post lists no extension API items at all, and chrome.crossOriginStorage didn't make the branch (more below). Chrome 159 branched on November 9 and goes stable December 8 — the last train out of 2026.

Every AMO developer has a new agreement to accept; the policies start December 1

Mozilla announced on October 28 that enterprise add-ons launch on addons.mozilla.org on December 1, through a dedicated enterprise release channel. Versions submitted there follow new enterprise add-on policies: they self-declare with the manifest key "admin_install_only": true under browser_specific_settings.gecko, they don't appear on AMO, and Mozilla won't distribute them in any other way. The phrase Mozilla uses is "deployed, not discovered" — IT admins install them across managed fleets with Firefox enterprise policies. Consumer listings keep using the normal submission path.

If you sell to IT-managed fleets, this is your official lane: reviewed and policy-blessed, at the cost of zero consumer discoverability. It formalizes the Firefox side of the B2B extension market, shaped like Chrome's force-install/policy ecosystem — my read, not something the announcement says.

But the part that touches every Firefox publisher is the paperwork. The new enterprise policies are folded into the updated Firefox Add-on Distribution Agreement, and per Mozilla's FAQ, every developer on AMO has to accept it, enterprise or not. Mozilla names no deadline: the instruction is to accept the updated agreement "when prompted", and the new policies take effect December 1. The current policies stay in effect until then, and the full policy text will be published on Extension Workshop. The post doesn't spell out what happens to a submission while the prompt sits unanswered — and I don't want to find out mid-submission. When the prompt shows up, two minutes then beats a publishing surprise later.

MessageSender.windowId: live in Firefox 160, merged in WebKit

Two updates on the season's most cross-browser new property (WECG #1077).

First, Firefox. Firefox 160 shipped on November 10 — the date W45 gave — per Mozilla's release history. The windowId commit (f43deb1ab6b2) is in it, so the property is in a stable browser for the first time. The rest of the Firefox 160 package shipped with it, including the aarch64 → arm64 change in runtime.getPlatformInfo(); W45 has the checklist.

Second, Safari. The issue now carries implemented: safari: WebKit merged the property on October 28 (PR 78537), and Apple's xeenon endorsed Firefox's semantics on the way — when no window is determinable, the property is omitted, which in their words "works better with JavaScript's ?? or ||." No WINDOW_ID_NONE sentinel in either implementation. It is not in a Safari release yet: neither the 27.2 notes nor the 27.3 beta notes mention it. So feature-detect rather than version-gate:

const targetWindow =
	"windowId" in sender ? sender.windowId : sender.tab?.windowId
// undefined = no determinable window — or a browser that hasn't shipped it yet

Chrome remains the holdout: labeled supportive in the group, with an open bug and no implementation announced. Orion has it marked as planned. Keep the sender.tab?.windowId / runtime.getContexts() fallback for Chrome and Safari; on Firefox 160+, code that routes messages from popups, side panels or devtools panels can stop the window-identification dance.

Safari's quiet week: cold-launch injection fixed, getPopup fix merged

The Safari 27.2 release notes (October 26, build 20625.2.8) carry exactly one Web Extensions item, and it's a good one: "Fixed a significant delay before web extension content is injected when Safari is cold launched." If you ship retry loops or late-injection fallbacks against Safari's startup race, test them on 27.2 — they may be up for retirement. Nothing breaks. For the wider Safari picture, see our Safari 27 features rundown.

On the standards side, Safari's relative-path divergence in action.getPopup() is on its way out: WECG #1142 closed on November 5, labeled implemented: for Chrome, Safari, Firefox and Orion. Safari returns a relative path (/popup.html) where everyone else returns the full chrome-extension://{id}/popup.html; WebKit merged the switch to the full URL on October 29 (PR 78787). It has not reached a Safari release — neither the 27.2 notes nor the 27.3 beta notes list it — and mdn/browser-compat-data#31057 was opened to record the version once it does. Keep path-vs-URL normalization for Safari until then.

One to watch: the Safari 27.3 beta notes (first published November 3, via Apple's release-notes index) list a substantial Web Extensions batch — the offscreen API, setAccessLevel() for storage.local and storage.sync, scripting.ExecutionWorld, plus five resolved issues including DNR static-vs-session redirect priority and webRequest events for DNR-blocked loads. No stable date for 27.3 yet.

Two WECG verdicts: required-features is dead, autofill declaration moves on

Required/optional feature declarations were rejected. WECG #1153 — the proposal for manifest keys like required_features / ignore_compatibility — closed November 5, labeled opposed: for Chrome, Safari and Firefox after that day's group meeting. The closing note is blunt: "Currently there is no appetite to figure something out cross-browser when it comes to declaring required / optional extension features. If browsers want something like this it can live in a browser_specific_settings subkey." The motivating pain — Orion on iOS showing "may not be compatible" prompts for extensions that declare sidebar_action / side_panel but work fine without them — keeps its spurious prompts. Per-browser subkeys are the sanctioned fragmentation, and each browser still has to choose to honor them. Declaration implies requirement; don't build tooling around either key.

dom.didPerformAutoFill() survived TPAC. On October 29 the group resolved on the proposal — an API for extensions to declare "I autofilled this form" so the browser can skip its own password-save prompt or style the fill: "Safari is interested in implementing this API; Firefox and Chrome are neutral and plan to implement it as a no-op. Next steps is an official proposal for the group to review." The no-op plans are the developer-friendly part: cross-browser code could call it unconditionally, with no feature-detection burden, once it's specified. More interesting is a November 9 follow-up comment proposing a dom.onDidPerformAutofill event, so autofill providers can learn about fills they didn't originate — a provider-to-provider channel. If you ship a password manager, that thread is where your input actually shapes something. Everyone else: nothing has shipped; don't build against it.

The M160 watch list: crossOriginStorage slips to January, and a browser-crash fix

Two Gerrit items now point at Chrome 160 — branch November 30, stable January 5, 2027, after the holiday gap (schedule). Both expected-only; neither merged.

chrome.crossOriginStorage missed two branch points. CL 8605006 (the MV3-only API: paged getEntries, removeEntry by hash, a coalesced payload-free onChanged) and its DNR companion haven't moved since October 28, missing M158's branch and the November 9 M159 branch. The Chrome 158 beta post listing no extension items confirms it isn't riding 158. Earliest realistic ship is now M160, stable January 5 — and with review idle for two weeks, a further slip is realistic. The design is unchanged since the October proposal: a new crossOriginStorage permission, MV3 only, with an install prompt reading "Read and delete files that sites share with each other". The webRequest variant stays abandoned — declarative DNR control, not observation, is the sanctioned design. Nothing breaks for anyone who ignores it; if you ship a privacy or cleaner tool, you have two more months to weigh whether COS visibility replaces your cross-origin-sharing heuristics.

A browser-process crash is live in stable, and it isn't your fault. CL 8716376 (created November 3, in review) fixes a genuinely nasty one: when onHeadersReceived is dispatched with null original response headers — a proxy-auth challenge on a CORS preflight, reachable with webRequest + extraHeaders — a blocking listener that returns responseHeaders, even unmodified, crashes the whole browser process. The kicker: the DNR path needs no webRequest at all — a modifyHeaders rule on response headers, the kind ad-blockers and header-rewriters ship, is enough on its own to reach the same null merge. The fix returns early on null headers, mirroring an earlier DNR fix. The race is narrow but the blast radius is the entire browser, and until this ships, the crashing pattern is live in stable. No extension-side action — don't rip out your response-header rules over it — but if your crash reports correlate with proxy-authenticated networks, watch the CL. Expected M160.

The rest of the frame

  • Chrome's dated calendar now runs ten consecutive milestones deep. Schedules for 168, 169 and 170 are on Chromium Dash: stable April 27, May 11 and May 25 of 2027, holding the 14-day cadence that has M161–M170 shipping between January 19 and May 25, 2027. Deprecation windows expressed in milestones now convert to firm dates well into mid-2027 — and the branch point, not the stable date, remains the real cutoff for what rides a release.
  • Where the platforms stand as of November 11: most users are still on 157, which got a patch release on November 9 — 157.0.8103.51 on Windows and Mac, .50 on Linux and Android. The 158 early-stable builds from November 4 (158.0.8127.18 on Windows and Mac, .22 on Android) reach only part of the population, and iOS joined with 158.0.8127.32 on November 10. Chrome 158 goes full stable November 17, late stable November 18.
  • Firefox kept its two-week rhythm: 159 on October 27 (no extension API changes), the 159.0.1 dot release on November 3, 160 on November 10.

What I'd do this week

  1. Run the 157 audit now if you skipped it — this is production behavior. Four greps: branches on clearAll() results, publicSuffix calls that take user- or URL-derived strings, webRequest/DNR code that promises full navigation coverage, and anything touching X-Chrome-Manage-Accounts. W45 has the checklist, W42 the deep dive.
  2. AMO publishers: accept the updated Firefox Add-on Distribution Agreement when AMO prompts you — the new policies take effect December 1. If you sell to IT fleets, weigh the enterprise channel ("admin_install_only": true, channel-only submission from December 1) against your current self-distribution setup.
  3. Firefox 160 is live — write the windowId detection once: "windowId" in sender, undefined = no determinable window, sender.tab?.windowId fallback for Chrome and Safari. If you skipped W45's Firefox 160 checklist, those changes are in stable now.
  4. Safari publishers: test cold-launch injection timing on 27.2 and retire late-injection workarounds that no longer fire. Keep getPopup() normalization: the full-URL fix is merged in WebKit and not yet in a Safari release.
  5. Password managers: weigh in on WECG #954 — specifically the onDidPerformAutofill event idea. It's the part that changes provider-vs-provider behavior, and the thread is open.
  6. Check your code against this week's changes. npx @extenshi/cli@latest advise . finds the four Chrome 157 changes — now live in the stable channel — in your extension with the file and line. It runs locally and needs no account. Every change we track is listed at cli.extenshi.io/changes. And if you want the full second pair of eyes before your next store upload, npx @extenshi/cli scan gets you 3 scans + 10 reads free with a free account (one-time); prepaid packs past that.

Sources

  • Chromium Dash — Stable channel releases (fetched 2026-11-11) — Chrome 157.0.8103.38/.39 on Windows/Mac and .38 on Linux/Android 2026-11-03, iOS .37 the same day; 157.0.8103.50/.51 patch builds 2026-11-09; Chrome 158.0.8127.18 on Windows/Mac and .22 on Android, 2026-11-04; iOS 158.0.8127.32 on 2026-11-10
  • Chromium Dash milestone schedules: M157 (stable 2026-11-03), M158 (early stable 2026-11-04, stable 2026-11-17, late stable 2026-11-18), M159 (branch point 2026-11-09, stable 2026-12-08), M160 (branch point 2026-11-30, stable 2027-01-05), M168, M169, M170 (stable 2027-04-27, 2027-05-11, 2027-05-25)
  • Chromium CLs shipping in M157: 8464103 (publicSuffix leading-dot rejection), 8182627 (alarms.clearAll() → Promise<undefined>, kill-switch present), 8497010 (webRequest/DNR initiator checks against user-restricted sites), 8501321 (X-Chrome-Manage-Accounts hidden on Gaia URLs), 8507256 (MV2 contextMenus types marked nodoc)
  • Chrome 158 beta post (2026-10-28) — no extension API items listed
  • "Introducing Enterprise Add-on Policies" — Mozilla Add-ons Blog, 2026-10-28: December 1 launch and effective date, "admin_install_only": true under browser_specific_settings.gecko, "deployed, not discovered", updated Firefox Add-on Distribution Agreement to be accepted by every AMO developer "when prompted" (no deadline stated), full policy text to be published on Extension Workshop
  • WECG #1077 — MessageSender.windowId: implemented: firefox (2026-10-17) and implemented: safari (2026-10-29) labels, Apple's absent-property endorsement (xeenon, 2026-10-27); Firefox commit f43deb1ab6b2 (Bug 2072133, committed 2026-10-16); WebKit PR 78537 (merged 2026-10-28); Chromium bug 579968332 — community-filed, open; Orion feedback 14560 — tagged Planned
  • Mozilla product-details, fetched 2026-11-11: major releases (159.0 on 2026-10-27, 160.0 on 2026-11-10), stability releases (159.0.1 on 2026-11-03)
  • Safari 27.2 release notes — released 2026-10-26, build 20625.2.8: "Fixed a significant delay before web extension content is injected when Safari is cold launched. (185268822)", the only Web Extensions item; Safari 27.3 beta notes first published 2026-11-03, neither listing windowId or getPopup via Apple's Safari release notes
  • WECG #1142 — action.getPopup() full-URL parity, closed 2026-11-05 with implemented: labels for chrome/safari/firefox/orion; WebKit PR 78787 (merged 2026-10-29, not yet in a Safari release); mdn/browser-compat-data#31057 — opened 2026-11-05 to pin the historical Safari relative-path behavior to a version
  • WECG #1153 — required/optional extension features proposal, closed 2026-11-05 with opposed: labels for chrome/safari/firefox, applied after the 2026-11-05 meeting; browser_specific_settings subkey quoted from the closing note
  • WECG #954 — dom.didPerformAutoFill(): TPAC resolution 2026-10-29 (kiaraarose), dom.onDidPerformAutofill event follow-up 2026-11-09 (bbruneau); issue open awaiting a formal proposal
  • Chromium CLs 8605006 + 8605007 — chrome.crossOriginStorage API and DNR blocking by hash, unmerged as of 2026-11-11 (both last updated 2026-10-28); CL 8606266 — webRequest variant, abandoned 2026-10-18
  • Chromium CL 8716376 — null-response-headers browser-process crash in webRequest/DNR header modification (created 2026-11-03, still in review on 2026-11-11; Fixed: 581338044), mirroring crrev.com/c/7014893
  • Extension Pulse 2026-W45 and 2026-W42 — the in-depth coverage this issue carries forward

Methodology

The generator's window for this issue returned thirteen forecast-pipeline signals, all fetched 2026-11-09 from primary sources and re-checked on November 11, before this issue was sent: Chromium Dash release and schedule feeds, Gerrit CL status checks, WECG issue state, Mozilla product-details and the Add-ons Blog, WebKit pull requests, and Apple's release notes. Nothing beyond those docs is stated here. Chrome 157's change list carries forward the W42 and W45 deep dives, re-dated against the live stable release. Both Gerrit items — crossOriginStorage and the null-headers crash fix — are unmerged as of the fetch: watch, not build. Scheduled dates move; treat November 17, December 1, December 8 and January 5 as calendars, not promises.


This issue of Extension Pulse is compiled from Chromium Dash and Chromium Gerrit, W3C WebExtensions Community Group issues, Mozilla release data and the Add-ons Blog, and Apple release notes. We don't independently verify every upstream claim, and references to specific projects or companies reflect the findings of the cited sources — not accusations of intentional wrongdoing. If something here is off, tell us at [email protected].

Previous issue (W45) → · Browse the catalog →

Related Articles