Everything You Ever Wanted To Know About Cross-Browser Web Extensions
summary
Shows that a working cross-browser extension is just a manifest plus a few JS/HTML files: a three-file demo uses a manifest.json and a background script to turn a page red, loads unpacked in Chrome developer mode, requires manual reload and debugger via the service worker, and packages to a zip for store upload with a small registration fee. Notes Chrome forcing manifest v3 while Firefox and Safari lag. A real project, Listeri, uses React + Parcel to capture a tab, upload a base64 image to backend, and deliver screenshot+annotation.
AI-written summary · about
chapters (12)
- 0:00Introduction to extensions
- 1:25What is an extension?
- 2:22History of extensions
- 3:48Standardization and v3
- 6:14Getting started with code
- 8:35The deployment process
- 10:54Live demo setup
- 13:21Writing a simple extension
- 17:21Developer workflow
- 20:06Browser compatibility issues
- 22:11Building a real extension
- 26:04Q&A session
related talks
38mBuilding Cross-Platform Browser Add-ons
33mBecome a wizard and make the browser your own
41mCross browser extensions – lets make one
22mExtending the Web - explore new UI surfaces with WebExtensions
15mCross Browser Add-ons and How to build one
33mBrowser Extensions
22mCross browser extensions - lets make one
01mEntrevista