Repository navigation
v0.808.0
Changes
- Add
Request.Reload()to queue a browser reload for connected or pending pages. Connected requests wake immediately; pending pages send Reload after successful connection setup. (#533) - Wake request processing automatically when browser commands are queued or dirty work is assigned. Maintenance also wakes requests with queued output. Dirty rendering retains its normal update interval.
- Make Reload the final WebSocket record: send it, close the connection, and cancel the Request. The browser disables connection recovery when reloading.
- Clarify guidance for composing standard widgets, bindings, and getters. (#532)
Upgrade notes
- All Reload commands, including session and global reloads, close the WebSocket after delivery. Later queued records are discarded; send logout redirects through HTTP.
- Events and callbacks continue until the Request is cancelled. State-based changes should still use
Dirtyto serialize rendering through the update loop.
Validation: PR checks passed, including race and production test suites, browser tests, linters, and the 32-bit CI job. Queue delivery, Request lifecycle, maintenance, and dirty-work benchmarks are recorded in #533.
Full changelog: v0.807.0...v0.808.0