https://github.com/fa0311/fix_chrome_search_on_github
Fix Chrome search on Github
https://github.com/fa0311/fix_chrome_search_on_github
chrome-extension github
Last synced: about 1 month ago
JSON representation
Fix Chrome search on Github
- Host: GitHub
- URL: https://github.com/fa0311/fix_chrome_search_on_github
- Owner: fa0311
- License: other
- Created: 2023-08-04T18:49:57.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2023-08-04T18:55:59.000Z (almost 3 years ago)
- Last Synced: 2025-04-06T06:58:43.598Z (about 1 year ago)
- Topics: chrome-extension, github
- Language: CSS
- Homepage:
- Size: 14.6 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# fix_chrome_search_on_github
This repository provides a **stable, reliable workaround** for a GitHub UI bug on Chrome, as shown in the screenshot below. The fix is applied via a **user style (User CSS)** and is designed to work consistently once enabled.
---
## What this does
When GitHub’s search pages break in Chrome (overlapping layouts, an unusable page, unexpected layers covering the UI, etc.), this user style restores a normal, usable layout.
This fix works by ensuring only the intended top-level content container remains visible, preventing the broken/duplicated top-layer containers from interfering with the page.
---
## Installation (Recommended: Stylus)
Since Chrome does not provide a convenient built-in way to apply per-site CSS, using a dedicated extension is the easiest and most stable approach.
### 1) Install Stylus
Install the **Stylus** browser extension from the Chrome Web Store.
### 2) Create a new style for GitHub
1. Click the Stylus icon
2. Choose **New style**
3. Set the target to `github.com` (or restrict it to search pages only — recommended)
4. Paste the CSS below
5. Save and enable
---
## CSS
```css
body>div:nth-child(n+2) {
display: none;
}
---
## Update (Added later)
**This issue has already been fixed on GitHub’s side.**
This repository (and the User CSS snippet) is kept for historical reference and for anyone who might still encounter similar rendering regressions in specific environments (e.g., older Chrome builds, cached assets, enterprise-managed browsers, etc.).
If you are no longer seeing the bug, you can safely disable or remove the style.