v0.50.262 — Two UX fixes (single-PR release)
Two unrelated UX bugs, both small surgical fixes with regression tests. Same shape as v0.50.255 (PR #1411). Self-built and independently reviewed by nesquena.
Fixed
+button (andCmd/Ctrl+K) was a no-op while the first message was streaming (#1432) — the empty-session guard from #1171 was checking onlymessage_count===0, which is true the entire time the first user turn is in-flight. Users couldn't actually open a parallel chat until the first response finished. The guard now also requires!S.busy && !S.session.active_stream_id && !S.session.pending_user_message— same in-flight signal already used by_restoreSettledSession()inmessages.js:1081. Reported by @Olyno.- Profile name field auto-capitalized typed values despite the "lowercase only" hint (#1423) — the input had
autocomplete="off"but was missingautocapitalize/autocorrect/spellcheckattributes, so mobile keyboards (iOS Safari / WKWebView / Android Chrome) silently capitalized the first letter and desktop spellcheck could rewrite the value on blur. The form lowercases on submit, so stored data was always correct — the bug was a misleading display during typing. Same attributes added to Base URL.
Stats
- 5 files changed, +163 / –10
- 3648 tests pass (+8 new regression tests, was 3640)
- CI: all 3 Python runners (3.11, 3.12, 3.13) green
- Independent review:
nesquena✅ (7-scenario behavioral matrix verified)
PRs
- #1435 — single-PR release