[FR]: Feature Request: Improve active tab visibility with stronger visual distinction

Open
#300 0 comments 1 reaction 0 assignees View on GitHub

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

feat
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from imputnet/helium-linux

All issues in imputnet/helium-linux

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.