Tag

#axis proposal

42 posts tagged.

benchmarks

Does It Run in the Browser They Actually Have? A Proposed Browser-Support Axis for AI App Builder Output (September 2026)

A proposed benchmark axis for which browser engines a generated app can actually run in. Baseline defines widely available as 30 months of interoperability and names what it cannot see. Next.js floors at Firefox 111, Vite resolves its default to Firefox 114, and the preview pane reports a pass either way. Seven weighted signals, four postures, a ten-step protocol, and no scores.

19 min read126
benchmarks

What Happens When the Connection Drops? A Proposed Axis for Client Network Failure Handling (September 2026)

A proposed benchmark axis for what a generated app does when the user’s own connection fails mid-action. The HTML Standard defines navigator.onLine so that true means "might be online", and the Fetch Standard defines a failed request as a response with status zero, no headers and no body. Seven weighted signals, four postures, a ten-step protocol, and no scores.

18 min read109
#axis proposal · BuilderProof