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] updating expansion panels data causes incorrect index to be given #11225

Closed
gotenxds opened this issue Apr 24, 2020 · 5 comments
Closed
Labels
C: VExpansionPanels VExpansionPanels P: high The issue is of high importance T: bug Functionality that does not work as intended/expected

Comments

@gotenxds
Copy link

Environment

Vuetify Version: 2.2.23
Vue Version: 2.6.11
Browsers: Chrome 80.0.3987.163
OS: Windows 10

Steps to reproduce

in codepen:
Click the expansion panels, see index changes to 0 for the first panel and 1 for the second panel.
This is Ok

Click on the ADD MORE button, to add another item to the top of the list.

click on the first expansion panel, see that selected index is 2, but index of the item in the list is actually 0

Expected Behavior

Clicking on expansion panel should update with the correct index of the item in the actual data array

Actual Behavior

The expansion list is rendered correctly (in correct order) but items have incorrect indexes when updating v-model

Reproduction Link

https://codepen.io/gotenxds/pen/GRpWEvO?editable=true&editors=101%3Dhttps%3A%2F%2Fvuetifyjs.com%2Fen%2Fcomponents%2Fexpansion-panels%2F

@ghost ghost added the S: triage label Apr 24, 2020
@jacekkarczmarczyk jacekkarczmarczyk added the C: VExpansionPanels VExpansionPanels label Apr 26, 2020
@kflavin

This comment has been minimized.

@gotenxds

This comment has been minimized.

@Mert75 Mert75 removed the S: triage label Aug 14, 2020
@Mert75
Copy link
Contributor

Mert75 commented Aug 14, 2020

Kind of similar to #11405 where it happens on a VListItemGroup

@Mert75 Mert75 added P: high The issue is of high importance T: bug Functionality that does not work as intended/expected labels Aug 14, 2020
@adatdeltax
Copy link

Has anyone found a workaround for this issue?.

@johnleider
Copy link
Member

Duplicate of #8001

If you have any questions, please reach out to us in our Discord community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: VExpansionPanels VExpansionPanels P: high The issue is of high importance T: bug Functionality that does not work as intended/expected
Projects
None yet
Development

No branches or pull requests

6 participants