vercel / vercel/next.js

[dev-overlay] User Preferences <select> buttons only clickable on text, not entire button

Open
#80,299 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
142k
Forks
32.4k
Avg merge
2d 14h
Merged PRs (30d)
351

Description

Link to the code that reproduces this issue

https://github.com/teamleaderleo/cleaner-slate

(I added a PR #80300 to fix this)

To Reproduce
  1. Start the application in development (next dev).
  2. Click the on-screen indicator in the bottom left.
  3. Click "Preferences."
  4. Try to click anything other than the text bit of a selection.
Current vs. Expected behavior

I need to be able to click the whole display div/alleged button.

I can't.

Image

Provide environment information
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
  Available memory (MB): 16044
  Available CPU cores: 16
Binaries:
  Node: 22.16.0
  npm: 10.8.1
  Yarn: 1.22.22
  pnpm: 10.11.0
Relevant Packages:
  next: 15.4.0-canary.71 // Latest available version is detected (15.4.0-canary.71).
  eslint-config-next: 15.3.3
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.3
Next.js Config:
  output: N/A
Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I tested on Chrome and Edge on Windows 11.

Contributor guide

Open the 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.

Research direction

Start with the reproduction repository and run the app using next dev, then follow the indicator to Preferences and reproduce the select-button behavior. Review PR #80300 and compare it with the reported steps; done means the full displayed control, not only its text, responds to clicks.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, next.js, react
Domain
frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.