-
-
Notifications
You must be signed in to change notification settings - Fork 533
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
Button Issue Migrating 0.9.4.4 on RC 1 to 0.9.5 on .NET 6.0 RTM #3150
Comments
That's weird. Did you remove all the occurrences of What browser do you use? |
blazorise.js is removed, and I used the references from https://blazorise.com/docs/start (link rel and javascript). My F5 points to Edge Dev, same happens on Edge (Windows default). Same on Firefox (inprivate). So this is cross-browser (I never had that app open in Firefox ever) Edit: do note though that the page I initially land on has no Blazorise components on them (index -> then login -> then go to page that has Blazorise components on them) |
Hi, Same issues here After the migration to Blazorise 0.9.5, I am experiencing a strange sporadic error.
It seems that the rendered object does not exist.
the project is a dotnet 5 Blazor Server Web Application with render-mode = "Server" Any hint? |
Not at the moment. Any chance you could create a small project to reproduce the issue? |
Maybe Blazorise's JS runs before Blazor's JS is fully initialized? I have a bunch of JS loading in that app already, so it might be triggering that behavior (just an uneducated guess). And no, stripping down that solution is nigh on impossible. |
It is possible that JS keeps loading before the component is not fully initialized. Do you guys have any URL rewrite in your apps? @damianog I see you have |
@stsrki no URL rewrite I only used host alias instead localhost @christophwille do you use the NavigateTo ( no forced reload ) when it heppens? |
My navigation actually is the bog-standard left-menu from the Blazor template (NavLink component). |
@stsrki could you consider to configure an option to switch off the javascript lazy loading so I could include them on the _host page as the old way? |
That big of a change would break the API and would require rewriting most of the internals. So it is unlikely we would go back to the old way. Unless we are able to reproduce the issue on our side it would be hard to fix the issue. I was thinking, and this is just my assumption, maybe I can try to |
I'm seeing this error as well after upgrading from 0.9.3 to 0.9.5. |
Hey guys. Would you be willing to try the fix if I release it as a preview on MyGet? I want to make sure it is working properly before I release an official update. |
I can do that, sure. |
@christophwille It is now up. To get it follow https://github.com/Megabit/Blazorise#try-preview |
Tried 0.9.5.1-p1 - still getting an error
|
@christophwille Can you try again with 0.9.5.1-p2? |
No still errors out:
|
I'm in the dark and just guessing now. Without properly reproducing the error on my side it would be really hard to fix it 😥 I will try to see what else might be worth changing... |
Please see your Gmail email. Other than that - other libs that do this dynamic loading? |
Did you clear the cache after the last 0.9.5.1-p2? |
Edit: we emailed and were able to sort out the caching. I tried with Edge, Edge Dev, Chrome inprivate and Firefox inprivate - all work now. |
I used https://blazorise.com/news/release-notes/095 to do the migration. I see the following error on navigating to a page that has Blazorise components on it:
Funny thing is, the buttons do work, and on navigating to another page & then back this error doesn't come up again. Sadly this message doesn't give (at least) me a clue where to start looking - do you have any pointers for me what might be going on?
The app started on 5.0 and I migrated to 6 during the previews once the upload limits (JS interop limits) were lifted. All the time I also upgraded Blazorise along the way.
The text was updated successfully, but these errors were encountered: