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>
42 lines
1.7 KiB
HTML
42 lines
1.7 KiB
HTML
{% from "_macros.html" import icon %}
|
|
{#
|
|
The share panel's placeholder on a detail page.
|
|
|
|
It fetches `_share_panel.html` on load rather than being rendered inline, and
|
|
that is the whole change: the panel used to be checkboxes inside the
|
|
resource's *save form*, so a share only happened if you also saved the
|
|
resource, and the list of candidates was every group and every account on the
|
|
instance, unpaginated, on every detail page.
|
|
|
|
Sharing still grants *reading*. Two people editing one note with no history and
|
|
no merge is worse than the inconvenience of copying it, so there is no "can
|
|
edit" and its absence is deliberate rather than missing.
|
|
|
|
Only the owner sees it at all — someone a thing was shared with cannot share it
|
|
onward — and the route enforces that as well, because a template is not a
|
|
permission check.
|
|
#}
|
|
{% if is_owner and can_share %}
|
|
<div hx-get="/api/library/share/{{ share_kind }}/{{ share_id }}"
|
|
hx-trigger="load"
|
|
hx-target="this"
|
|
hx-swap="outerHTML">
|
|
{# The shape of what is coming, rather than an ellipsis that says only that
|
|
something is missing. `aria-hidden` and a `role="status"` label beside it,
|
|
because a paragraph of grey blocks is nothing to read aloud. #}
|
|
<section class="card">
|
|
<h2 class="card__title">Shared with</h2>
|
|
<span class="visually-hidden" role="status">Loading who this is shared with</span>
|
|
<div aria-hidden="true">
|
|
<div class="skeleton skeleton--row"></div>
|
|
<div class="skeleton skeleton--row skeleton--short"></div>
|
|
</div>
|
|
</section>
|
|
</div>
|
|
{% elif not is_owner %}
|
|
<div class="alert">
|
|
{{ icon("users", "alert__icon") }}
|
|
<span>Shared with you. You can read this but not change it.</span>
|
|
</div>
|
|
{% endif %}
|