Read the source,
not the announcement.
Primary documentation and compatibility pages stay attached to every claim.
NEW55 field notes · 8 capabilities Understand what's next.
Understand what's next.
Use what makes sense.
A practical publication about browser capabilities, their limits, and the fallbacks that make adoption thoughtful. Start with a real need, then follow the evidence.
CHROME✳FIREFOX✳SAFARI✳EDGE✳W3C✳MDN✳CANIUSE✳
CAPABILITIES / 08Native dialogPopoverContainer size queriesView transitionsCSS anchor positioningResizeObserver
◉ BASELINE / CHECKED
Native dialog
Present a focused confirmation or short task in a modal window, with browser-managed modality through the dialog element.
CHROMEFIREFOXSAFARILIVE
FALLBACKProvide the task as an ordinary linked page or visible section first.
PRIMARY SOURCEMDN / W3C / HTML spec
CHECKS ON FILE32
THE PRACTICE
New is not the same
as useful.
Every capability arrives with a promise and a set of conditions. We publish the conditions: the support, the fallback, the source, and the moment it makes sense to adopt.
The point is not to be first. The point is to know what happens when the feature is absent.
How we read a specTHE PRACTICAL LAYER
Read the spec.
Keep the fallback.
Ship on purpose.
Read the specification
Start with the primary source. The explainer is not the contract.
Check the implementations
A support table is a snapshot, not a promise. Note the date and the version.
Plan the fallback
Every new capability needs a path for the person who does not have it yet.
Keep the evidence
A decision is easier to revisit when the source and the reason are still visible.
Every note names the page, the decision, and the limit. The archive is a record, not a certainty.
Browse the field notes ↗THE CURRENT RECORD
OpenAI Claims ChatGPT Search Hits 20% of Google's Query Volume
The figure came from an OpenAI executive at a press event, not from independent measurement, and leaves key comparison details unconfirmed.
Read the note ↗THE FIELD NOTES
What's next,
carefully.
A reading list of changes, methods, and evidence. Every entry keeps its source — and all 55 notes are in the archive.
All 55 notes ↗01 / Status · November 4, 2026
OpenAI Claims ChatGPT Search Hits 20% of Google's Query Volume
The figure came from an OpenAI executive at a press event, not from independent measurement, and leaves key comparison details unconfirmed.
Read the note 02 / Status · November 3, 2026Arc Browser Shuts Down December 22 as Maker Shifts to Dia
Here is what on-call teams relying on Arc need to verify before the December 22 cutoff, and what The Browser Company has not yet detailed.
Read the note 03 / Status · November 2, 2026GitHub CLI Adds Opt-In Expiring OAuth Tokens After Credential-Theft Reports
GitHub's October 21 changelog entry lands weeks after security write-ups on the LiteLLM breach pointed to stolen CLI OAuth tokens as an attack vector.
Read the note 04 / Forms · October 9, 2026Cloudflare Turnstile Spin Lets an Agent Wire CAPTCHA Without Code Access
A new agent-mediated setup flow creates and embeds a Turnstile widget while keeping application source off Cloudflare's servers, raising fresh questions about what on-call teams need to verify before trusting the wiring.
Read the note 05 / Fallback method · October 6, 2026GitHub Stacked Pull Requests Reach General Availability Across All Plans
GitHub has turned on stacked pull requests for every github.com plan, with auto-merge and a Server release still to come.
Read the note 06 / Browser release evidence · September 7, 2026MDN Reframes showModal() Support as a Multi-Stage Check, Not a Yes/No Flag
A documentation update to HTMLDialogElement.showModal() splits browser support into separate checks for presence, interaction, input coverage, fallback, and rollback, changing how teams should read any single compatibility claim.
Read the noteWHY THIS PUBLICATION
A useful layer
over the changelog.
Specifications move, support shifts, and summaries lose the caveats. Useful Tomorrow keeps the practical layer: what shipped, where it works, and what to do when it does not.
Read the source,
Treat support
as a snapshot.
Dates and versions are part of the record. A table from last year is not today.
Make the fallback
part of the feature.
The page still works when the enhancement is absent. That is the design brief.
Keep the evidence
attached.
Specifications, MDN pages, and study files stay one click from the note.
Start with a real need. Read the source. Keep the fallback in view.