HomerandClaude Opus 5
28390095a9
The sidebar was a 280px panel laid over the page below the phone breakpoint, opened from first paint, with the only control that closed it underneath it -- and that control existed on /chat and on none of the seven other pages carrying a sidebar, Settings included. It starts closed at that width now, slides, dims the page behind it, and closes by tapping beside it, by Escape, or by its own button, which is inside the drawer where it can be reached. Everything a finger has to hit was 36px, or 28 for renaming a chat, every action on a message and every panel's close button. Raising --control-h under a coarse pointer is the only fix that reaches all forty of them, which is what that token is for. The row and message actions were also hover-only, so on a phone they did not exist at all. Installing: the splash and the browser chrome follow the instance's theme rather than always being Moria's near-black; there are screenshots, so the install offer is a dialog rather than a one-line bar; a new release no longer takes over a page somebody is reading; the notification badge is a silhouette rather than a grey square; and a browser rotating its own subscription no longer ends notifications for good. Every request now says it is happening -- nothing did before, so anything slower than a few milliseconds looked like a click that had not registered. A chat can be archived. The column has been filtered on in four places since folders arrived and written by nothing, which is what made it look built. chat.css may contain media queries. The ban protected the composer toolbar from being "fixed" with a breakpoint; that guarantee is asserted directly now, and the old test would have passed a version of the file that wrapped the toolbar without one. scripts/shoot.py is the instrument all of this was found with: it renders a page through TestClient into a real headless browser at a real size and refuses to run if an asset URL was left pointing at testserver. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
38 lines
1.4 KiB
HTML
38 lines
1.4 KiB
HTML
{#
|
|
One page of older turns, oldest first, plus a fresh sentinel above them when
|
|
there is more.
|
|
|
|
No root element, and the sentinel replaces *itself* with this whole fragment
|
|
(`hx-swap="outerHTML"`), so each page lands exactly where the previous
|
|
sentinel was and the next one ends up at the top again.
|
|
|
|
The turns are rendered by `chat/_message.html`, the same template as
|
|
everything else in the thread. That is what makes scrolling up look identical
|
|
to scrolling down: there is no second way of drawing a message here, so there
|
|
is nothing that could drift from it.
|
|
#}
|
|
{% if more_before %}
|
|
{#
|
|
`hx-target="this"` is stated rather than inherited. This fragment is swapped
|
|
into a page whose composer form carries `hx-target="#thread"`, and htmx
|
|
resolves that by walking up the DOM -- the jobs chip has already demonstrated
|
|
once what an unstated target does to a transcript.
|
|
#}
|
|
<div class="history-sentinel"
|
|
hx-get="/api/messages/history?before={{ oldest_id }}"
|
|
hx-trigger="revealed"
|
|
hx-target="this"
|
|
hx-swap="outerHTML"
|
|
hx-sync="this:drop">
|
|
<span class="visually-hidden" role="status">Loading earlier messages</span>
|
|
<div class="history-sentinel__shape" aria-hidden="true">
|
|
<div class="skeleton skeleton--line"></div>
|
|
<div class="skeleton skeleton--line skeleton--short"></div>
|
|
</div>
|
|
</div>
|
|
{% endif %}
|
|
|
|
{% for message in messages %}
|
|
{% include "chat/_message.html" %}
|
|
{% endfor %}
|