Skip to content

fix(ui): restore pointer cursors for clickable controls - #10999

Merged
marius-kilocode merged 5 commits into
mainfrom
fix/clickable-pointer-cursors
Jun 8, 2026
Merged

fix(ui): restore pointer cursors for clickable controls#10999
marius-kilocode merged 5 commits into
mainfrom
fix/clickable-pointer-cursors

Conversation

@marius-kilocode

Copy link
Copy Markdown
Collaborator

Clickable controls in the webviews can render with the default cursor, making buttons and links difficult to distinguish from non-interactive content. The upstream desktop UI removed pointer cursors in commit 89b703c387 and made the default explicit in 6ba7c54bab; neither change came through a pull request. Kilo PR #6663 restored the cursor component by component, but native and ARIA controls remained dependent on individual styles and new gaps kept appearing, especially in Agent Manager.

Apply one low-specificity semantic cursor rule for enabled buttons, links, summaries, and common ARIA controls. Using :where() keeps specialized states authoritative, so disabled controls and drag targets retain their existing cursors while all Kilo webviews get consistent clickable feedback.

@marius-kilocode
marius-kilocode enabled auto-merge (squash) June 8, 2026 11:07
@kilo-code-bot

kilo-code-bot Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)
  • .changeset/bright-pointer-controls.md
  • packages/kilo-ui/src/styles/globals.css
  • .github/workflows/visual-regression.yml

Reviewed by claude-4.6-sonnet-20260217 · 185,698 tokens

Review guidance: REVIEW.md from base branch main

@marius-kilocode
marius-kilocode merged commit ad93990 into main Jun 8, 2026
20 checks passed
@marius-kilocode
marius-kilocode deleted the fix/clickable-pointer-cursors branch June 8, 2026 16:32
t7tran pushed a commit to t7tran/kilocode that referenced this pull request Aug 14, 2026
* fix(ui): restore pointer cursors for clickable controls

* fix(ci): raise VS Code Storybook heap limit

* fix(ci): extend heap to visual test server
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants