From 845bf062edb737d543f47023fa0c248a0ea271f3 Mon Sep 17 00:00:00 2001
From: Andreas Reinhold / reini <reini@kadenpartner.ch>
Date: Thu, 17 Sep 2026 15:38:11 +0200
Subject: [PATCH] Let the dashboard's sort dropdown span the shares card

The sort select above the admin dashboard's shares list was capped at
20rem by the admin-shares-sort wrapper. The wrapper and its rule in
app.css are gone, so the select stretches with the card's stack like
the other fields. CHANGELOG (Unreleased) notes it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---
 CHANGELOG.md                                  |  1 +
 resources/css/app.css                         |  9 ------
 .../livewire/admin/admin-dashboard.blade.php  | 30 +++++++++----------
 3 files changed, 15 insertions(+), 25 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index c228ae9..ef0f4fc 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -17,6 +17,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `docker-compose.example.yml` mounts `sealshare_database` at `/app/database/sqlite` and sets `DB_DATABASE` to the file in it. To switch an existing install, mount the same volume there and set `DB_DATABASE: /app/database/sqlite/database.sqlite` in both services; the database is kept.
 - A share that reached its download limit is closed at once, but deleted by the hourly cleanup 24 hours after its last download instead of immediately, so downloads still running can finish. Until then its files still count towards the storage quota.
 - The download page of a share with a download limit says how many downloads are left, or how long the recipient can still download. The admin dashboard shows downloads as "2 of 3 downloads", marks shares at their limit as "Download limit reached" and no longer counts them as active.
+- The sort dropdown on the admin dashboard spans the full width of the shares card.
 
 ## [2.1.0] - 2026-09-16
 
diff --git a/resources/css/app.css b/resources/css/app.css
index 00afa2b..c9dc491 100644
--- a/resources/css/app.css
+++ b/resources/css/app.css
@@ -289,15 +289,6 @@
     max-inline-size: 24rem;
 }
 
-/*
- * resources/views/livewire/admin/admin-dashboard.blade.php: the sort select above the shares list
- * keeps to the width its longest option needs instead of spanning the card. No `<x-select>` width
- * prop caps it, and 20rem matches no `<x-pane>` preset.
- */
-.admin-shares-sort {
-    max-inline-size: 20rem;
-}
-
 /*
  * resources/views/livewire/admin/admin-dashboard.blade.php: a share's details are two lines of
  * their own (its files, size and downloads; its expiry), and they wrap rather than clip. The
diff --git a/resources/views/livewire/admin/admin-dashboard.blade.php b/resources/views/livewire/admin/admin-dashboard.blade.php
index 62b9e7b..5d9ac91 100644
--- a/resources/views/livewire/admin/admin-dashboard.blade.php
+++ b/resources/views/livewire/admin/admin-dashboard.blade.php
@@ -9,27 +9,25 @@
     </x-grid>
 
     {{-- The shares as a list, not a table: a table's columns need more than the page's 40rem, and
-         every page keeps that one width. The sort is a select above the list instead of column headers. --}}
+         every page keeps that one width. The sort is a full-width select above the list instead of column headers. --}}
     <x-card :title="__('All Shares')" heading="h2" variant="outlined">
         <x-stack gap="space200">
             @if ($shares->total() === 0)
                 <x-empty-state icon="link_off" :title="__('No shares yet')" :description="__('Shares appear here once someone uploads files.')" />
             @else
-                <div class="admin-shares-sort">
-                    <x-select
-                        wire:model.live="sort"
-                        :label="__('Sort by')"
-                        :options="[
-                            ['id' => 'newest', 'name' => __('Newest first')],
-                            ['id' => 'oldest', 'name' => __('Oldest first')],
-                            ['id' => 'expiring', 'name' => __('Expiring soonest')],
-                            ['id' => 'largest', 'name' => __('Largest')],
-                            ['id' => 'most-downloaded', 'name' => __('Most downloads')],
-                            ['id' => 'most-files', 'name' => __('Most files')],
-                        ]"
-                        data-test="shares-sort"
-                    />
-                </div>
+                <x-select
+                    wire:model.live="sort"
+                    :label="__('Sort by')"
+                    :options="[
+                        ['id' => 'newest', 'name' => __('Newest first')],
+                        ['id' => 'oldest', 'name' => __('Oldest first')],
+                        ['id' => 'expiring', 'name' => __('Expiring soonest')],
+                        ['id' => 'largest', 'name' => __('Largest')],
+                        ['id' => 'most-downloaded', 'name' => __('Most downloads')],
+                        ['id' => 'most-files', 'name' => __('Most files')],
+                    ]"
+                    data-test="shares-sort"
+                />
 
                 {{-- Each share fits the column on a phone: the token opens it, so delete is the one button;
                      the details are two short lines that never clip (admin-shares, app.css). --}}