CHABOTSearch

Topic

Browsers

Technical writing on browsers.

All technical writing

2026

  1. A browser that writes down the form instead of sending it

    An agent-first browser engine runs a click the way page code expects, then records a form submission and stops, leaving network access, protocol transport, threads and session state with the application that embeds it.

    BrowsersAgent systemsRuntimeArchitecture

  2. A desktop can look correct and still lose your work

    A Firefox Undo that could take a whole note sat beside 5,550 passing screenshot comparisons. What pixel checks, behavioural journeys, store readback and honest reports each catch in a React rebuild of macOS Catalina.

    VerificationBrowsersReact

  3. A failed save should leave the person’s work where they can recover it

    What a form owes you when the server refuses your text: where the only copy lives while a request is in flight, how a task board and a shared document editor were repaired, and how to test a refusal without hiding it.

    EditingFormsConflictsVerificationBrowsers

  4. A video call is more than connecting two media streams

    Why an old tab’s hang-up must not end the call that replaced it: numbered seats, idempotent joins, a per-person claim and whole-description signalling in a browser WebRTC demo with no TURN relay.

    WebrtcBrowsersConcurrencyArchitecture

  5. One desktop, many windows, and the changes that arrive late

    In a browser rebuild of Catalina, remounting the menu bar kept closing the person’s live stream. How to give each long-lived resource an owner with the right lifetime, and how numbered changes tell a page’s own late writes from someone else’s.

    BrowsersReactConcurrencyArchitecture

  6. The test passed, but the person still could not do the thing

    What a browser test has to establish beyond a 200 or a successful click, followed along a new user’s path from documentation to clipboard to the app and its dashboard.

    SelectedVerificationBrowsersRelease engineering