Repository navigation
Show the arrow cursor on controls and the hand only on links and cards - #1361
Merged
Merged
Conversation
manuelmayer-dev
added
improvement
manuelmayer-dev
deleted the
refactor/native-desktop-cursor-conventions
branch
October 14, 2026 04:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by the maintainer (no GitHub issue).
Summary
Buttons, switches, tabs, menu rows and sliders now show the arrow cursor in the desktop UI, the web client and the bootstrapper windows. The hand stays on links, cards, deck tiles and clickable content, and plugin dialog buttons and value controls follow the same rule. A new test keeps the hand off ordinary controls.
Testing
Desktop UI, web client, runtime and bootstrapper tests pass, plus the new cursor test and the Angular build. I read the computed cursor in a running desktop UI (all pages and settings) and on the web client login. A real plugin dialog and the bootstrapper windows were not exercised. Three unrelated .NET tests failed locally: the screen lock test, the CLI build test and a TLS test that passes alone.
Checklist