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.

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

Height for a <v-expansion-panel> elment not set to auto intially #718

Closed
marlohaering opened this issue Jun 7, 2017 · 3 comments
Closed
Assignees
Labels
T: bug Functionality that does not work as intended/expected

Comments

@marlohaering
Copy link

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

@johnleider johnleider added the T: bug Functionality that does not work as intended/expected label Jun 7, 2017
@johnleider johnleider self-assigned this Jun 7, 2017
johnleider added a commit that referenced this issue Jun 10, 2017
@marlohaering
Copy link
Author

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.

@johnleider
Copy link
Member

The fix has not released yet.

@lock
Copy link

lock bot commented Apr 16, 2019

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

@lock lock bot locked as resolved and limited conversation to collaborators Apr 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
T: bug Functionality that does not work as intended/expected
Projects
None yet
Development

No branches or pull requests

2 participants