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.7.1] vAutocomplete: ResizeObserver loop completed with undelivered notifications #20444

Open
func0der opened this issue Sep 9, 2024 · 1 comment

Comments

@func0der
Copy link

func0der commented Sep 9, 2024

Environment

Vuetify Version: 3.7.1
Vue Version: 3.5.3
Browsers: Firefox 129.0
OS: Linux x86_64

Steps to reproduce

  1. Open the console
  2. Choose an item of the left autocomplete with multiple.
  3. Find the error in the console

Expected Behavior

Prevent error from happening

Actual Behavior

Triggers error every time an item is chosen.

Reproduction Link

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

Other comments

Especially with an error handler this is a very noticable error.

@cintek
Copy link

cintek commented Oct 8, 2024

The same issue occurs with v-select (using Vuetify 3.6.14). In my case I used it in this structure:

<v-data-table-server>
  <template v-slot:thead>
    <tr>
      <td>
        <template>
          <v-select />
        </template>
      </td>
    </tr>
  </template>
</v-data-table-server>

This problem is gone when using v-select inside v-row and v-col. You can see it in this example (modified version of the one by @func0der) :
https://play.vuetifyjs.com/#eNqtUkFuwjAQ/Moql4AEicQRBaS+oUfCIY031MLxWrYTKiH+3rVDSwgSqiouTnZmvZ7xeHdOnK3zN2OyvsNknRQeW6Mqj9tSAxT9sjIm/nIhZA+1qpzblIlYNgq/yuTKxVZLp98yAjWpERAhhwprPwYBpAgDLRlBJ10m92S/bEmg4o7WHabkWrLcIIeMl6TdlG875aVReI/Wn9K4MZSPZedT3f80snrq5IGdWnloeIGXUN9CKnIOdIiZ8SHnIh/lz6WrrTQeHPpueAayNWQ9nMFiAxdoLLWQ8tNJQzvLYeUe2B9sQsdst5/f4KszpnZpQ5QuIP2obPhU7iiOlRPHuPxU6f5u5OrJzMD9fWjYfpKaU8pIo7VkeTvCZhuHksJM0WGGmad3b6U+zOZ8YpEPl8HXkFwWulMqLvtvrzH0oA==

But in my code if I would use v-row and v-col it would break the layout so I would appreciate it to see this issue fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants