You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A simple v-expansion-panel with two v-expansion-panel-content elements. In case the first v-expansion-panel-content element is extended intially already and the height increases when shrinking the width of the browser window, it overlaps the second v-expansion-panel-content below.
Versions
Tested with MacOS and Windows with latest version of Google Chrome.
"vue": "^2.2.1"
"vuetify": "^0.12.0"
What is expected ?
The height should adapt automatically.
What is actually happening ?
The first v-expansion-panel-content elements overlaps the second one.
I think the bug is not fully fixed yet. I changed the above mentioned codepen slightly by wrapping each of the two v-expansion-panel-contents in it's own tag. The problem is still present.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please direct any non-bug questions to our Discord
lockbot
locked as resolved and limited conversation to collaborators
Apr 16, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
T: bugFunctionality that does not work as intended/expected
Steps to reproduce
A simple v-expansion-panel with two v-expansion-panel-content elements. In case the first v-expansion-panel-content element is extended intially already and the height increases when shrinking the width of the browser window, it overlaps the second v-expansion-panel-content below.
Versions
Tested with MacOS and Windows with latest version of Google Chrome.
"vue": "^2.2.1"
"vuetify": "^0.12.0"
What is expected ?
The height should adapt automatically.
What is actually happening ?
The first v-expansion-panel-content elements overlaps the second one.
Reproduction Link
https://codepen.io/king10002/pen/jmdRZP?editors=1010
The text was updated successfully, but these errors were encountered: