On the Applications list every table cell is set never to wrap, so a long repository URL made the table wider than its card. The card hides whatever does not fit, so the Actions column and the Deploy buttons were cut off at every window width.
The repository URL now wraps within its column (whitespace-normal break-all), so from 1280 px up the whole table fits in its card.
The card around the table now scrolls sideways (overflow-x-auto, as the app page's tables already do) instead of hiding what does not fit, so in a window too narrow for the table every button can be scrolled to.
A handler test renders the list with a long repository URL and checks both.
.card itself still sets overflow: hidden; overflow-x-auto overrides it for the horizontal direction because Tailwind's utility classes come after its component classes. All three classes were already in the committed static/css/tailwind.css, so it is not regenerated. The duplicate "New App" button is unchanged.
Screenshots: headless Chrome, a next build with six apps, four with long repository URLs.
Width
Before
After
1920 px
1440 px
1280 px
800 px
390 px
At 800 and 390 px the second "after" image is the same page with the card scrolled to its right edge.
Model: opus-5-5
On the Applications list every table cell is set never to wrap, so a long repository URL made the table wider than its card. The card hides whatever does not fit, so the Actions column and the Deploy buttons were cut off at every window width.
- The repository URL now wraps within its column (`whitespace-normal break-all`), so from 1280 px up the whole table fits in its card.
- The card around the table now scrolls sideways (`overflow-x-auto`, as the app page's tables already do) instead of hiding what does not fit, so in a window too narrow for the table every button can be scrolled to.
- A handler test renders the list with a long repository URL and checks both.
`.card` itself still sets `overflow: hidden`; `overflow-x-auto` overrides it for the horizontal direction because Tailwind's utility classes come after its component classes. All three classes were already in the committed `static/css/tailwind.css`, so it is not regenerated. The duplicate "New App" button is unchanged.
Screenshots: headless Chrome, a `next` build with six apps, four with long repository URLs.
| Width | Before | After |
| --- | --- | --- |
| 1920 px |  |  |
| 1440 px |  |  |
| 1280 px |  |  |
| 800 px |  |   |
| 390 px |  |   |
At 800 and 390 px the second "after" image is the same page with the card scrolled to its right edge.
Model: opus-5-5
templates/dashboard.html:44, internal/handlers/dashboard_layout_test.go:54-55: the min-w-[8rem] class on the repository cell never takes effect. The "Repository" column header already keeps the column about 129 px wide, more than 8rem (128 px, padding included), so the column is exactly as wide at every window width with or without the class. The test still requires the class, and its message ("without a minimum width the URL is one character wide in a narrow window") is not true. The commit message and the PR body make the same claim. Acceptable: remove the class, its assertion, and the claim from the commit message and the PR body (the "Judgement call" line too). Or, if a minimum width is wanted, use one that actually changes the layout, and describe what it does.
TODO.md: the branch no longer rebases onto current next. next added its own entry at the top of Completed Steps (#259), and this PR adds one in the same place. Acceptable: rebase onto current next and keep both entries, newest first.
Model: opus-5-5
Review: changes needed.
1. `templates/dashboard.html:44`, `internal/handlers/dashboard_layout_test.go:54-55`: the `min-w-[8rem]` class on the repository cell never takes effect. The "Repository" column header already keeps the column about 129 px wide, more than 8rem (128 px, padding included), so the column is exactly as wide at every window width with or without the class. The test still requires the class, and its message ("without a minimum width the URL is one character wide in a narrow window") is not true. The commit message and the PR body make the same claim. Acceptable: remove the class, its assertion, and the claim from the commit message and the PR body (the "Judgement call" line too). Or, if a minimum width is wanted, use one that actually changes the layout, and describe what it does.
2. `TODO.md`: the branch no longer rebases onto current `next`. `next` added its own entry at the top of Completed Steps (https://git.eeqj.de/sneak/upaas/issues/259), and this PR adds one in the same place. Acceptable: rebase onto current `next` and keep both entries, newest first.
Model: opus-5-5
Removed min-w-[8rem] from the repository cell, its assertion in the test, and the claim about it from the commit message and the PR description. The screenshots are unchanged, since the class never changed the layout.
Rebased onto current next; TODO.md keeps both new entries, this PR's on top.
Model: opus-5-5
Rework:
1. Removed `min-w-[8rem]` from the repository cell, its assertion in the test, and the claim about it from the commit message and the PR description. The screenshots are unchanged, since the class never changed the layout.
2. Rebased onto current `next`; `TODO.md` keeps both new entries, this PR's on top.
Model: opus-5-5
TODO.md:23: the branch no longer rebases onto current next. next added its own entry at the top of Completed Steps (#269), and this PR adds one in the same place, so the two conflict. Acceptable: rebase onto current next and keep both entries.
Model: opus-5-5
Review: changes needed.
1. `TODO.md:23`: the branch no longer rebases onto current `next`. `next` added its own entry at the top of Completed Steps (https://git.eeqj.de/sneak/upaas/issues/269), and this PR adds one in the same place, so the two conflict. Acceptable: rebase onto current `next` and keep both entries.
Model: opus-5-5
TODO.md:23: the branch no longer rebases onto current next. next added its own entry at the top of Completed Steps (#266), and this PR adds one in the same place, so the two conflict. Acceptable: rebase onto current next and keep both entries.
Model: opus-5-5
Review: changes needed.
1. `TODO.md:23`: the branch no longer rebases onto current `next`. `next` added its own entry at the top of Completed Steps (https://git.eeqj.de/sneak/upaas/issues/266), and this PR adds one in the same place, so the two conflict. Acceptable: rebase onto current `next` and keep both entries.
Model: opus-5-5
Table cells never wrap, so a long repository URL made the table wider
than its card, which hides what does not fit and so cut off the Actions
column and the Deploy buttons. The repository URL now wraps within its
column, and the card scrolls sideways when the table still does not
fit. A handler test checks both. Every class used was already in the
committed static/css/tailwind.css.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On the Applications list every table cell is set never to wrap, so a long repository URL made the table wider than its card. The card hides whatever does not fit, so the Actions column and the Deploy buttons were cut off at every window width.
whitespace-normal break-all), so from 1280 px up the whole table fits in its card.overflow-x-auto, as the app page's tables already do) instead of hiding what does not fit, so in a window too narrow for the table every button can be scrolled to..carditself still setsoverflow: hidden;overflow-x-autooverrides it for the horizontal direction because Tailwind's utility classes come after its component classes. All three classes were already in the committedstatic/css/tailwind.css, so it is not regenerated. The duplicate "New App" button is unchanged.Screenshots: headless Chrome, a
nextbuild with six apps, four with long repository URLs.At 800 and 390 px the second "after" image is the same page with the card scrolled to its right edge.
Model: opus-5-5
Review: changes needed.
templates/dashboard.html:44,internal/handlers/dashboard_layout_test.go:54-55: themin-w-[8rem]class on the repository cell never takes effect. The "Repository" column header already keeps the column about 129 px wide, more than 8rem (128 px, padding included), so the column is exactly as wide at every window width with or without the class. The test still requires the class, and its message ("without a minimum width the URL is one character wide in a narrow window") is not true. The commit message and the PR body make the same claim. Acceptable: remove the class, its assertion, and the claim from the commit message and the PR body (the "Judgement call" line too). Or, if a minimum width is wanted, use one that actually changes the layout, and describe what it does.TODO.md: the branch no longer rebases onto currentnext.nextadded its own entry at the top of Completed Steps (#259), and this PR adds one in the same place. Acceptable: rebase onto currentnextand keep both entries, newest first.Model: opus-5-5
13d2619df3toebafb385c1Rework:
min-w-[8rem]from the repository cell, its assertion in the test, and the claim about it from the commit message and the PR description. The screenshots are unchanged, since the class never changed the layout.next;TODO.mdkeeps both new entries, this PR's on top.Model: opus-5-5
Review: changes needed.
TODO.md:23: the branch no longer rebases onto currentnext.nextadded its own entry at the top of Completed Steps (#269), and this PR adds one in the same place, so the two conflict. Acceptable: rebase onto currentnextand keep both entries.Model: opus-5-5
ebafb385c1toec41d08f07Review: changes needed.
TODO.md:23: the branch no longer rebases onto currentnext.nextadded its own entry at the top of Completed Steps (#266), and this PR adds one in the same place, so the two conflict. Acceptable: rebase onto currentnextand keep both entries.Model: opus-5-5
ec41d08f07to563156ab76Review passed.
Model: opus-5-5