[FR]: Feature Request: Improve active tab visibility with stronger visual distinction
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- desktop
Research direction
The payload names no files or entry points, so start by finding where the tab styling lives in the helium-linux repository. Pick one of the suggested options (accent line, background shade, or bold text) and confirm the direction with maintainers, since the issue has no replies yet. Done means the active tab is clearly distinct from inactive tabs in a screenshot on Linux.
Written by the indexing model from the issue text.
Description
Description
Improve active tab visibility with stronger visual distinction
Who's implementing?
- I'm willing to implement this feature myself
The problem
Hi Helium team,
First, thank you for building such a clean and lightweight browser. I really like the overall UI and performance.
I wanted to suggest a small usability improvement related to tabs. At the moment, the active tab is a bit difficult to identify quickly, especially when multiple tabs are open and I am working continuously. This is not a bug, but more of a UI comfort / accessibility improvement request.
Current behavior
The active tab does not stand out enough visually from inactive tabs. The difference feels too subtle, so it takes an extra moment to recognize which tab is currently selected.
Possible solutions
Requested improvement, especially in linux systems, like cachy os, where native ui is not great as macos or windowsos.
Please consider adding a stronger visual indicator for the active tab, such as:
- A clearer highlight
- An underline or accent line
- Stronger contrast between active and inactive tabs
- Slightly different background shade
- Optional bold tab text or more distinct border
Additional context
No response
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 63
- Avg merge
- 28m
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from imputnet/helium-linux
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
imputnet/helium-linux#385 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#459 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
imputnet/helium-linux#457 ·
Maintainers usually reply within 1 day
-
feat
Difficulty 3/5 1-2 days Newbie friendliness 48/100
imputnet/helium-linux#455 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#454 ·
Maintainers usually reply within 1 day
All issues in imputnet/helium-linux
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days