-
Notifications
You must be signed in to change notification settings - Fork 165
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
Client-side JS error when showing a Dialog with certain types of components on it #19548
Comments
Can you try to configure maven plugin with |
It worked! With setting this to false the errors gone and everything works fine! |
Can you please tell us if you are using reflection to load components? You can also have a look at this for more details: https://vaadin.com/docs/latest/production/production-build#bundle-component-loading-optimizations This setting is safe to use. You can also find out more about it here: https://vaadin.com/docs/v23/configuration/maven#build-front-end-goal-parametershttps://vaadin.com/docs/v23/configuration/maven#build-front-end-goal-parameters You have also mentioned that you used 23.4.10 version. Did you mean 24.3.10? |
We don't use reflections directly, but use Spring (not Spring-boot) which I think uses reflection. Yes, the correct version is 24.3.10! Fixed this in my opening comment as well. Thank you for your help! |
Description of the bug
When I try to pop up a Dialog in my application from a MenuBar element (using a Button as menu item, it's invoking the Dialog when clicked) with a ComboBox and/or a Grid on it, the Dialog shows but without the components, and there are JS exceptions on the console.
The following errors are shown on the console in Chrome:
Some observations and facts:
Expected behavior
The Dialog with a ComboBox and/or a Grid should show all the components added, without any client-side JS errors.
Minimal reproducible example
Open a Dialog with a ComboBox and/or a Grid on it, and it will open with client-side JS errors.
Versions
The text was updated successfully, but these errors were encountered: