-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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.
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
[Bug Report][2.6.2] VNavigationDrawe ,attr expandOnHover always enable(true) #14555
Comments
@iam993 |
@KareemDa |
@Ahriana |
yeah ive just bypassed the padding at the moment until i have the time to look into it more |
i dont think so as its applies earlier in the file instead, the behaviour is as if the side bar is always expanded, but the expand behaviour is the same as before but the content is pushed over as if the minivariant is being ignored in style but not behaviour |
This comment has been minimized.
This comment has been minimized.
|
I still have the issue, or maybe the doc needs an update because what was working in 2.5.10 is not working anymore with the same configuration expand-on-hover
disable-resize-watcher
hide-overlay
permanent
mini-variant-width="80px"``` |
What are you expecting vs what are you getting? I see no difference with the props you gave in 2.6.1 and 2.6.3, the bug in 2.6.2 seems to have been fixed in 2.6.3 |
Expecting Getting We were experiencing this issue in production where CI wasn't honoring the yarn.lock file and the Vuetify version was the last available (2.6.3). We didn't have this issue on our local env where we had v.2.5.10 so we fixed the issue bonding the package version to 2.5.10. We didn't had time to investigate more on this issue but if needed I can help to setup a codepen to reproduce it. |
Please follow #14585 |
Environment
Vuetify Version: 2.6.2
Last working version: 2.6.2
Vue Version: 2.6.9
Browsers: Chrome 89.0.4389.90
OS: Windows 10
Steps to reproduce
/
Expected Behavior
/
Actual Behavior
/
Reproduction Link
https://codepen.io/
Other comments
/
The text was updated successfully, but these errors were encountered: