Evolving Chrome Extensions with Manifest V3
summary
Manifest V3 asserts three concrete shifts: replace the blocking webRequest handler with a limited declarativeNetRequest rules JSON that can block facebook.com without host permissions; swap persistent background pages for evented service worker background scripts so state moves to chrome.storage and execution is ephemeral; ban remotely loaded code so third‑party libs must be bundled and exposed via web_accessible_resources and chrome.runtime.getURL; and default runtime host permissions to click‑to‑activate (activeTab) to reduce always‑on all_urls access.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:31Extension History Netscape Navigator 2.0
- 7:18Browser Extensions (later Add-ons) Firefox 1.0
- 16:00The Limitations of MV2
- 20:00Chrome Extensions - MV3 Goals
- 21:41Runtime Host Permissions
- 26:20Service Workers
- 30:58Remotely Hosted Code (RHC)
related talks
19mExtensions patterns for Manifest V3
27mOld new manifest and its inevitability
29mEverything You Ever Wanted To Know About Cross-Browser Web Extensions
45mWhat’s new in Chrome?
33mBecome a wizard and make the browser your own
01h 06mBrowser panel
41mChrome and the web in 2020
22mExtending the Web - explore new UI surfaces with WebExtensions