[FR]: Restore old window control behavior in native (aero) titlebar
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- desktop
Research direction
The payload names no files, tests or entry points, so begin by finding the existing native titlebar option in the repository and how it places the window controls. The request is to move the controls back into the titlebar row, ideally behind a separate toggle, so the issue alone does not say where the change belongs. Done means the controls sit in the titlebar for the Aero-style decorations, with the old placement still available by default.
Written by the indexing model from the issue text.
Description
Description
Move the titlebar buttons back from the separate row, restore chromium's aero titlebar behavior
Who's implementing?
- I'm willing to implement this feature myself
The problem
When using something like AeroThemePlasma, or other KDE window decorations (possibly also other desktop environments), the native titlebar option moves the window controls to a new row, instead of the titlebar just being in the style of the window decorations (which makes sense for those wanting the extra padding of the system titlebar added on top of helium's, but doesn't look as pretty or feel as great to use imo)
Possible solutions
I'm not sure how difficult of a request this would be as AFAIK upstream chromium removed the aero titlebar code ages ago, and the amount of users that'd benefit from this seems limited to just people with more customized linux installs (and windows themes I guess as well), but I wanted to ask here anyways as the current situation with it has been bothering me lol
A separate toggle for this style of titlebar would probably be the best way I can think of on the user's end? Just because there's no way to guarantee how functional it'd be with other window styles that haven't been tested and all
Current titlebar situation:
Chromium's previous aero titlebar behavior:
(not asking for the classic tab style option here though that might be a future FR on the main repo if it's something worth considering)
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