~/talk

Develop your own Browser extension

Talkat Voxxed Days Zurich 2026 · on Tuesday, 2026-03-24· [web-platform, developer-experience]
slides:none on file

Shows that a browser extension can be built like a frontend SPA and actually replaces repetitive dev tasks: a Chrome-only extension is created with Vite + React build and loaded unpacked, using a chrome.cookies API adapter to switch from window.document.cookie to extension APIs; it sets and removes auth cookies and successfully manipulates an active tab. Automation uses React Testing Library to drive a form flow and demos an automated 25-step journey. Notes Chromium vs Firefox compatibility.

AI-written summary · about

  1. 0:00Introduction
  2. 2:00Project challenge and idea
  3. 4:15Why extensions use JavaScript
  4. 6:02Loading local extension
  5. 8:36What extensions can do
  6. 10:01Manifest JSON and permissions
  7. 11:29Extension functionality with JavaScript
  8. 12:55SPAs for extensions
  9. 13:16Local dev and cookies
  10. 15:03Production build and Chrome API
  11. 16:49Testing production extension
  12. 17:33Automating user journeys
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.