Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug Report][3.1.7] VSelect menu in VDialog has wrong offset depending on scroll position #16850

Closed
avarixe opened this issue Mar 7, 2023 · 3 comments
Closed

[Bug Report][3.1.7] VSelect menu in VDialog has wrong offset depending on scroll position #16850

avarixe opened this issue Mar 7, 2023 · 3 comments
Labels
duplicate The issue has already been reported

Comments

@avarixe
Copy link
Contributor

avarixe commented Mar 7, 2023

Environment

Vuetify Version: 3.1.7
Vue Version: 3.3.0-alpha.4
Browsers: Chrome 110.0.0.0
OS: Windows 10

Steps to reproduce

  1. Create page long enough to require scrolling
  2. Add a VDialog in the middle
  3. Add a VSelect inside the VDialog
  4. Open VDialog when scroll position is NOT at the top
  5. Open VSelect

Expected Behavior

VSelect menu should appear below the selection field

Actual Behavior

VSelect menu appears way below the selection field, even offscreen if scroll is down enough

Reproduction Link

https://play.vuetifyjs.com/#...
@benoitkugler
Copy link

Probably a duplicate of #16663

@KaelWD
Copy link
Member

KaelWD commented Mar 7, 2023

Duplicate of #16770

@KaelWD KaelWD marked this as a duplicate of #16770 Mar 7, 2023
@KaelWD KaelWD closed this as not planned Won't fix, can't repro, duplicate, stale Mar 7, 2023
@KaelWD KaelWD added the duplicate The issue has already been reported label Mar 7, 2023
@github-actions github-actions bot removed the S: triage label Mar 7, 2023
@qxygene

This comment was marked as off-topic.

Sign in to view
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate The issue has already been reported
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@qxygene @avarixe @KaelWD @benoitkugler