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] Update of list not working correctly in combination of v-hover due to new vue scope #6643

Closed
qnp opened this issue Feb 28, 2019 · 2 comments
Labels
upstream Problem with a third party library that we may have to work around

Comments

@qnp
Copy link

qnp commented Feb 28, 2019

Versions and Environment

Vuetify: 1.5.4
Last working version: 1.5.4
Vue: 2.6.7
Browsers: Chrome 72.0.3626.119
OS: Mac OS 10.14.1

Steps to reproduce

Wrap v-list-tile with v-hover:

...
<v-hover v-for="(item, i) in items" :key="'item' + i">
    <v-list-tile
        :key="'issue' + i"
        slot-scope="scope"
        :class="scope.hover ? 'elevation-4 blue lighten-4' : 'elevation-1'"
    >
...
data() {
   return {
      items: [ ... ]
   },
},

Then remove an item from items and see what happens. See reproduction link.

Expected Behavior

This worked perfectly before I upgraded to vue 2.6.7:
Removing an item from items removed the correct one in the list.

Actual Behavior

When you remove an item from items, you effectively have one less item in the list by all the data is not refreshed properly as if it was the last item which have been removed.

Reproduction Link

https://codesandbox.io/s/r78l4lnk5n

Other comments

It seems to be a problem with new vue slots and slot-scope

@KaelWD KaelWD added the upstream Problem with a third party library that we may have to work around label Feb 28, 2019
@KaelWD
Copy link
Member

KaelWD commented Feb 28, 2019

@qnp
Copy link
Author

qnp commented Mar 1, 2019

Thanks @KaelWD for creating a vue issue and linking to it.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream Problem with a third party library that we may have to work around
Projects
None yet
Development

No branches or pull requests

2 participants