Hi,
In the release notes of v25.1.38 this bug is noted as fixed.
However it wasn't fixed when we tested it on our projects.
So we tested it on the playground and there it was OK.
The reason is that your javascript is different on the CDN comparing to the javascript packaged in the library.
How is that possible ? What is your process allowing to publish two different code under the same version number ?
Same for 25.1.39.
Depending on if we use the CDN or the library file it could behave differently.
Regards,
Julien
Hi Julien Barach,
Thank you for getting back to us. We've thoroughly validated your requirement, and we apologize for any confusion caused. We're pleased to inform you that the fix for the reported issue has indeed been included in the Syncfusion package version 25.1.39.
Throughout our testing process, we made sure to verify compatibility with both the Syncfusion package and CDN reference. For your convenience, we've included the CDN reference in the attached sample. Please take a moment to review the provided sample for further reference.
For more information about CDN, kindly check out the below documentation.
Documentation: https://blazor.syncfusion.com/documentation/common/cdn-fallback
Regards,
Yohapuja S
Hi,
Yes the bug is now fixed in 25.1.39.
But I'm wondering why you still have different Javascript file between CDN and packaging (even 25.1.39). This can lead to several issues.
Regards,
Hi Julien Barach,
Thank you for reaching out to us. We understand that you are encountering an issue with our dropdown component after upgrading to version 25.2.39 of the Syncfusion package. To assist you better, could you please provide us with detailed information about the issue you are facing? This information will help us thoroughly validate the problem and offer you accurate suggestions or solutions.
Here are some specific details we would appreciate receiving:
Description of the Issue: Please describe the problem you are experiencing with the dropdown component in as much detail as possible. Include any error messages, unexpected behavior, or specific scenarios where the issue occurs.
Steps to Reproduce: If possible, provide step-by-step instructions on how to reproduce the issue. This will allow us to recreate the problem on our end and investigate it effectively.
Code Snippets: If applicable, please share any relevant code snippets related to the usage of the dropdown component. This could include markup, JavaScript/TypeScript code, or any configuration settings.
Screenshots or Videos: If you have any screenshots or videos demonstrating the issue, please share them with us. Visual aids can provide valuable context and help us better understand the problem.
By providing us with this detailed information, we will be able to conduct a thorough investigation and provide you with the appropriate assistance to resolve the issue. Thank you for your patience and cooperation.
Regards,
Yohapuja S
Hi,
Sorry if I'm not clear.
There is no issue with the dropdown anymore. 25.1.38 showed a consequences of the issue below :
The issue is that your CDN JS file is different than the JS file packaged in the NuGet source.
I am asking why.
I've compared two versions for the JS file :
- 25.1.38 : CDN vs packaged are different
- 25.1.39 : CDN vs packaged are different
Regards,
Hi Julien Barach,
We have checked this general query with the respective team, and we have branched this query to a separate forum. You can track the progress and receive updates by the following forum link provided below:
Regards,
Yohapuja S