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][3.5.17] Failed to execute 'observe' on 'ResizeObserver' #19713

Closed
ker-nicolaib opened this issue Apr 29, 2024 · 8 comments · Fixed by #19731, Enterprise-CMCS/cmcs-eregulations#1315 or LLotme/esp-idf#19 · May be fixed by LLotme/esp-idf#5 or LLotme/esp-idf#12
Assignees
Labels
C: VDatePicker VDatePicker C: VOverlay VOverlay C: VVirtualScroll T: bug Functionality that does not work as intended/expected
Milestone

Comments

@ker-nicolaib
Copy link

Environment

Vuetify Version: 3.5.17
Vue Version: 3.4.25
Browsers: Chrome 124.0.0.0
OS: Windows

Steps to reproduce

Change the Version of Vue to 3.4.24 or 3.4.25. Then just add v-for to the v-select Tag like v-for="item in [1,2,3]".
Then click on one of the select-fields.

Expected Behavior

No Error should appear in the Browser Console.

Actual Behavior

An Error appears in the Browser Console.

Reproduction Link

https://play.vuetifyjs.com/#...

@yuwu9145
Copy link
Member

yuwu9145 commented May 1, 2024

The error seems to only occurs when manually change Vue version and tweaking code at the same time.

The error couldn't be replicated when Vue version & code stays the same, they don't change when running a project. demo

Is this issue causing any issue in your project?

@KaelWD
Copy link
Member

KaelWD commented May 1, 2024

Looks like https://vuejs.org/guide/essentials/template-refs.html#refs-inside-v-for but the v-for is sometimes leaking through the slot which would make sense if the ref wasn't also provided by the slot.

@naka87003
Copy link

I have same issue. In my case, it is not possible to change the value.
So we refrain from upgrading vue from 3.4.23.
How can I fit that?

@KaelWD
Copy link
Member

KaelWD commented May 1, 2024

Same thing here actually: #19685

I can reproduce both of these in our dev environment but not play.vuetifyjs.com

@yuwu9145
Copy link
Member

yuwu9145 commented May 1, 2024

Pass in :ref="el => {}" to slot rootv-list-item stops v-for leaking it to an array, could be a workaround.

@KaelWD
Copy link
Member

KaelWD commented May 1, 2024

that'll break the virtual scrolling

@yuwu9145
Copy link
Member

yuwu9145 commented May 1, 2024

What about :ref="el => props.ref.value = el"

@yuwu9145 yuwu9145 self-assigned this May 4, 2024
@yuwu9145 yuwu9145 added T: bug Functionality that does not work as intended/expected C: VDatePicker VDatePicker C: VOverlay VOverlay C: VVirtualScroll and removed S: triage labels May 4, 2024
@KaelWD KaelWD added this to the v3.6.x milestone May 7, 2024
@KaelWD KaelWD self-assigned this May 7, 2024
KaelWD added a commit that referenced this issue May 7, 2024
fixes #19713
fixes #19685

Co-authored-by: Kael <kaelwd@gmail.com>
@ker-nicolaib
Copy link
Author

Hello @yuwu9145 and @KaelWD ,
thank you for your efforts :-)
So will this Problem be fixed in the next Version of Vuetify?

mariadb-ThienLy added a commit to mariadb-corporation/MaxScale that referenced this issue Jun 24, 2024
When using `v-for` with `VSelect` component, the mentioned error
appears in the console, preventing users from selecting an item.

This was a bug in Vuetify, as mentioned here:
[Vuetify Issue #19713](vuetifyjs/vuetify#19713).

This bug was fixed in version 3.6.4 so this migrates vuetify to
that version.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment