The bar's rule for its own field (.searchbar input) also matched every input in the advanced panel, which sits in the same form, so the text fields lost their borders and the checkboxes shrank to nothing. That happened at any width, not only on phones. On a phone the panel also hung from the search field, which is a sliver between the menu, logo and account buttons, so the Cancel and Search buttons were pushed out of it. Reported on the forum (t/232, with a screenshot).
The rule now covers only the bar's own field. At phone width the panel spans the top bar in one column, the button row wraps and the panel scrolls if it runs short. It also closes on a tap outside it, on Escape and on a page change, since the bar stays on screen across pages. Checked with the built stylesheet in headless Chromium at 390px and 1280px; the before render matches the reported screenshot.
The bar's rule for its own field (`.searchbar input`) also matched every input in the advanced panel, which sits in the same form, so the text fields lost their borders and the checkboxes shrank to nothing. That happened at any width, not only on phones. On a phone the panel also hung from the search field, which is a sliver between the menu, logo and account buttons, so the Cancel and Search buttons were pushed out of it. Reported on the forum (t/232, with a screenshot).
The rule now covers only the bar's own field. At phone width the panel spans the top bar in one column, the button row wraps and the panel scrolls if it runs short. It also closes on a tap outside it, on Escape and on a page change, since the bar stays on screen across pages. Checked with the built stylesheet in headless Chromium at 390px and 1280px; the before render matches the reported screenshot.
Fixes #94
The bar's rule for its own input (`.searchbar input`) matched every
input in the advanced panel too, since the panel sits in the same form:
the text fields lost their borders, the checkboxes shrank to nothing.
That was true at any width. On a phone the panel also hung from the
search field, which is only what the menu, logo and account buttons
leave, so it was a sliver with its buttons pushed out of it.
The rule now covers only the bar's field. At phone width the panel
spans the top bar in one column, the button row wraps, and the panel
scrolls if it runs short. It also closes on a tap outside it, on
Escape and when the page changes, since the bar stays on screen.
Fixes#94
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.
The bar's rule for its own field (
.searchbar input) also matched every input in the advanced panel, which sits in the same form, so the text fields lost their borders and the checkboxes shrank to nothing. That happened at any width, not only on phones. On a phone the panel also hung from the search field, which is a sliver between the menu, logo and account buttons, so the Cancel and Search buttons were pushed out of it. Reported on the forum (t/232, with a screenshot).The rule now covers only the bar's own field. At phone width the panel spans the top bar in one column, the button row wraps and the panel scrolls if it runs short. It also closes on a tap outside it, on Escape and on a page change, since the bar stays on screen across pages. Checked with the built stylesheet in headless Chromium at 390px and 1280px; the before render matches the reported screenshot.
Fixes #94