Pull-new branch dropdown is transparent: page text shows through under the options #236
Labels
No labels
actions
bug
cli
duplicate
enhancement
fork
forum
git storage
help wanted
insights
invalid
issues
moderation
oidc
ownership transfer
packages
pr/merge protection rules
projects
pull requests
question
releases
sponsorships
tags
webhooks
wiki
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
crueber/walhub#236
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What's wrong
On the open-a-pull-request page (
/:owner/:name/pulls/new), the head/base branch dropdown renders as a transparent panel — the page content underneath it shows through and overlaps the option text, making the picker hard to read.Root cause (code evidence)
The dropdown in
web/src/pages/PullNew.jsx:82uses:The only stylesheet rule for
.ref-listisweb/css/repo.css:81:It has no background, border, box-shadow, or opaque color — it's a floating
absolutepanel over the page, so everything beneath bleeds through. The properly styled dropdown class in the same file,.ref-drop(repo.css:74-78), has exactly what's missing:background: var(--panel); border: 1px solid var(--border); border-radius: 8px; box-shadow: 0 8px 24px ….The option rows have the same problem:
ref-item(PullNew.jsx:88) has no CSS rule anywhere in the repo, while the styled equivalent.ref-row(repo.css:82-86) does — withbackground: noneit would still be transparent even if the panel weren't.Note this affects both pickers on the page (head and base use the same
RefSelectcomponent, PullNew.jsx:34-105). The identical dropdown markup inweb/src/pages/Pull.jsx:218(ref-list absolute z-10 …for the reviewer picker) almost certainly has the same transparency bug — fix both.Expected
The dropdown is an opaque panel (panel background, border, shadow — i.e. the
.ref-droptreatment) and each option row is readable with a hover highlight. Nothing underneath shows through, in both light and dark themes.Acceptance criteria
/:owner/:name/pulls/newrender as opaque panels:var(--panel)background, border, shadow, readable in light and dark themes..ref-row-equivalent styling for.ref-item).web/src/pages/Pull.jsx:218gets the same fix.Fixed by #245 (branch fix/issue-236): both dropdowns now wire the shared #115 opaque-popover classes (ref-drop card) with hover-highlighted rows, dark + light, no new CSS. node --test 460/460 green, vite build clean. Not merged — awaiting review.
Review of PR #245 (fix/issue-236, opaque branch picker dropdowns):
WIRING (both pickers on the shared #115 opaque pattern):
ref-list ref-drop card scroll-slim absolute z-10 mt-1 max-h-48 w-full overflow-y-auto p-1 shadow-lg. Opaque coreref-drop cardmatches the Repo.jsx:282 picker; layout deltas (ul vs div, w-full/z-10/mt-1/p-1/shadow-lg vs w-80/z-30/mt-2/p-2) are correct for an inline under-input list. Scroll (scroll-slim max-h-48 overflow-y-auto) + stacking (absolute z-10) preserved.ref-itemhook, add explicittext-zinc-800 dark:text-zinc-200+hover:bg-zinc-100 dark:hover:bg-zinc-800— readable + hover-highlighted in both themes (explicit text color is arguably better than Repo.jsx:307 rows, which inherit).CONSTRAINTS (AGENTS.md laws 1/8/12):
git diff main...origin/fix/issue-236 --name-onlyconfirms zero .css/package.json changes. Dead web/css/repo.css untouched (correct, out of scope).TEST:
ref-list absoluteremaining, behavior unchanged (150ms debounce, refStream/suggest, pick-to-close), live-stylesheet wiring (ui.css imports + .ref-drop opaque rule).vite buildsucceeds; compiled CSS contains the opaque rule:.ref-drop,...{background-color:white}+ dark.dark{zinc-900}variant. (One env note: an early full-suite run showed ERR_MODULE_NOT_FOUND for marked — artifact of running before web/node_modules was linked in scratch, not a PR issue; clean re-run is green.)No fixes needed; nothing pushed. MERGE RECOMMENDATION: ready to merge.
Fixed by PR #245 (review clean; both pickers on the shared opaque pattern; 460/460), merged. Closing.