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

[Bug Report] V-tab not displayed initially inside dialog #5401

Closed
ScreamZ opened this issue Oct 23, 2018 · 7 comments
Closed

[Bug Report] V-tab not displayed initially inside dialog #5401

ScreamZ opened this issue Oct 23, 2018 · 7 comments
Assignees
Labels
P: low The issue is of low importance T: bug Functionality that does not work as intended/expected T: regression Something that used to work but we broke
Milestone

Comments

@ScreamZ
Copy link

ScreamZ commented Oct 23, 2018

Versions and Environment

Vuetify: 1.3.2
Last working version: 1.2.9
Vue: 2.5.17
Browsers: Chrome 69.0.3497.100
OS: Mac OS 10.14.0

Expected Behavior

Should display first tab initially

Actual Behavior

Display blank, click on second it display second click back on first display first

Reproduction Link

Edit Vue Template

@KaelWD KaelWD added T: bug Functionality that does not work as intended/expected T: regression Something that used to work but we broke P: low The issue is of low importance and removed P: low The issue is of low importance labels Oct 24, 2018
@KaelWD
Copy link
Member

KaelWD commented Oct 24, 2018

See #1978. v-window should not be setting a height initially, but it isn't really a huge problem as you should already be using a workaround so the slider is displayed properly.

@KaelWD KaelWD added the P: low The issue is of low importance label Oct 24, 2018
@ScreamZ
Copy link
Author

ScreamZ commented Oct 24, 2018

So the issues is that when it is rendered and not displayed, the calculation take a 0px for heightfor computation? Using lazy prevent this ?

Thanks for the tips, could be nice to have a disclaimer in the doc of vtabs

@KaelWD
Copy link
Member

KaelWD commented Oct 24, 2018

Would be nicer to fix the bug 😉

@KaelWD
Copy link
Member

KaelWD commented Oct 24, 2018

This may be related to #5410

@ScreamZ
Copy link
Author

ScreamZ commented Oct 24, 2018

@KaelWD Allright, will take a look when I have a moment :)

@johnleider
Copy link
Member

This has been resolved as a result of 4af99de for #5410

@johnleider johnleider self-assigned this Oct 24, 2018
@johnleider johnleider added this to the v1.3.x milestone Oct 24, 2018
@ScreamZ
Copy link
Author

ScreamZ commented Oct 24, 2018

@johnleider Good job homie. Thanks for the rapidity :)

@ScreamZ ScreamZ closed this as completed Oct 24, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P: low The issue is of low importance T: bug Functionality that does not work as intended/expected T: regression Something that used to work but we broke
Projects
None yet
Development

No branches or pull requests

3 participants