Select component in Actions is slow to show results

[meyer59]

• Laravel Version: 10.37.3
• Nova Version: 4.32.9
• PHP Version: 8.2
• Database Driver & Version: MYSQL
• Operating System and Version: UNIX
• Browser type and version: chrome 119.0.6045.124

Description:

We have noticed an issue with the Select component in our Actions; it doesn't seem to be working properly after the latest update of Nova. The issue manifests as a significant lag in the visual response, giving the impression of extensive processing taking place in the background. This behavior started occurring since the most recent update of Nova.
This is very annonying since the Select component is used everywhere in the app.
Here is a screenshot of the console, the last log appears once i open the Select

Detailed steps to reproduce the issue on a fresh Nova installation:

put a searchable select in an action and try to open it

[henryavila]

The but was introduced in v4.32.7, sol, downgrading to v4.32.6 will work

[meyer59]

(Don't tag maintainers) is there any way to prioritize this bug? It seems to be affecting all of the Nova Select components.

[crynobone]

Please check if the latest version (4.32.15) still has this issue.

[meyer59]

yes it's better but we cannot close the Select.
Also can you remove the Console pollution ? There are plenty of plugin with webpack/vite to remove them in prod build
Thanks

[crynobone]

yes it's better but we cannot close the Select.

Please provide video of this.

[meyer59]

screen-capture.11.mp4

[crynobone]

[meyer59]

That's weird. can you check now with an mp4 file.

[crynobone]

This code was removed on v4.32.10, are you sure you're on the latest version?

[meyer59]

My bad, i forgot the nova:publish command. Now the console is cleared but the Select still doesn't close, as shown in the video.

[meyer59]

Hey
I don't know if it's related to the fix but the Select doesn't work anymore.
Keeps open, cannot select a value nor search.
Nova v.4.32.16

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.