Files
jmiller d16b417a24 fix(issues): make custom-status select render its options (visibility bug)
The issue-view "status" control was a native <select> carrying the fomantic
"ui compact dropdown" class. Fomantic enhanced it into an overlay menu that
rendered mispositioned and stacked BEHIND .issue-content, so the status options
were present in the DOM but invisible (a raised z-index did not rescue it — the
menu was trapped in an ancestor stacking context). Nothing in web_src/js depends
on it being a fomantic dropdown.

Drop the fomantic class so it stays a plain native <select> (the browser renders
its option list, so the options always show), and move the element's inline
style= into a new stylesheet web_src/css/repo/issue-status.css (imported from
index.css), per the "no inline styles" standard.
2026-07-16 12:28:57 -05:00

18 lines
683 B
CSS

/* Custom issue-status control.
Kept as a plain native <select> (NOT a fomantic ".ui dropdown"): when this
element carried the "ui compact dropdown" class, fomantic enhanced it into an
overlay menu that rendered mispositioned and behind .issue-content, so the
status options were present in the DOM but invisible. A native <select>
renders its option list via the browser, so the options always show.
Styles moved here from an inline style= attribute on the element. */
.issue-status-select {
min-width: 140px;
padding: 7px 10px;
color: var(--color-text);
border: 1px solid var(--color-secondary);
border-radius: 4px;
background: var(--color-body);
}