Pictures are taken as they arrive, not waited for
The document comes on another thread, the window live meanwhile
Fetching ahead, together: the pool, the preload scanner, the rules that still hold
TLS: a second connection to a server resumes the first, in 1.3 by ticket and in 1.2 by ticket or session id
Frames: an iframe draws its document under the framing rules; the root's top margin; WPT 9286
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ebXZs43Ks9pd5MerR62rG
Brotli of our own and web fonts in WOFF2; WPT 9249
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ebXZs43Ks9pd5MerR62rG
The cache: freshness, heuristics, revalidation and the profile's cache folder
Content Security Policy: what is enforced, where it is judged, and what is left
Networking: revocation lists and the hello's extension rules on Linux
Networking: the Linux client speaks TLS 1.2 as well
The TLS section says what the client negotiates now, in 1.3 and, for a
server with nothing newer, in 1.2: both AEADs, both groups, RSA or
ECDSA, the extended master secret, and never renegotiation; that CRL
fetching is what still keeps it short of the badssl gate; the two
environment variables that narrow a hello; and the five seconds a
connection gives each address. Not written yet no longer says a
TLS-1.2-only or AES-only host cannot load on Linux, and names what is
still missing there: revocation and session resumption.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ebXZs43Ks9pd5MerR62rG
fetch and XMLHttpRequest: Scripting, Networking, Not written yet
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EkzH8EAowXWrPXkiKyR9f6
The Linux window: Running Sashfold, Building, Architecture, Networking, Not written yet
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EkzH8EAowXWrPXkiKyR9f6
The user-agent example says 0.0.5
Organize the wiki: a Home index by category, the pages that carry the details, and the C++ rationale under Design decisions
Home is an index in five categories — getting started, what works
today, measured, design decisions, testing and tools — with a sidebar
on every page. The details that lived in the README's paragraphs move
into pages of their own (Building, Running Sashfold, Themes, Parsing,
Styling, Layout, Painting and text, Networking, The shell, Not written
yet, Measurements, The Sashfold 100, The Pledge, Security defaults,
Testing, Scripting the shell), each with headings, lists and tables.
The C++ rationale becomes the Why C++ page under Design decisions,
its five points kept and its prose tightened.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Aat76GqxAyBf9VRJ4QaUbK