-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Failed to execute 'insertBefore' on 'Node': Nodes of type '#text' may not be inserted inside nodes of type '#document' #48574
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
Comments
cc @danroth27 @SteveSandersonMS let me know if I am just doing something dumb here. |
Hi @isaacrlevin. Thanks for reporting this issue! Nothing immediately jumps out to me as being wrong in your code. I have a Blazor SSR sample with streaming rendering setup on the FetchData page that you can also compare with. |
Thanks @danroth27 The only main difference is that I just have one component with the full html doc in there, not using |
Not that I was aware of, but I guess there is now 😄 |
Well let me know if there is any more info you need. I can put what I have in a repo if that helps. |
Thanks for reporting this. This problem should go away naturally once we implement #47258 as we'll no longer be trying to rebuild the DOM entirely from the root component node. |
@mkArtak @SteveSandersonMS Should we close this as a duplicate of #47258 then? |
I'd keep it open so that we only close it once we've confirmed in reality that my claim is true. |
I don't want to piggyback on this issue, but I thought that I would comment that I've pulled down Dan Roth's Github repo (https://github.com/danroth27/BlazorSSR) as well as created a new Blazor WebApp from the new template, and have found that the StreamRendering attribute is doing nothing. The whole page loads all at once. Should I create a new issue for this? |
@mohaaron Make sure you disable CSS hot reload. It's a known incompatibility with streaming rendering that we are in process of fixing. |
That did it, thank you! |
This issue is now addressed in #48945, though perhaps not in the way originally anticipated. While dealing with this, it became obvious that root components should not allow interactive rendering, because that would make it impossible to place |
Is there an existing issue for this?
Describe the bug
FULL DISCLOSURE I MIGHT BE DOING SOMETHING WRONG
I am trying to wire up StreamRendering for a quick prototype using SSR. When I add the
@attribute [StreamRendering(true)]
to a RazorComponent that is configured for SSR, I get the following error in the browser dev tools.Expected Behavior
For the component to render before the async tasks complete as described in this blog post
https://devblogs.microsoft.com/dotnet/asp-net-core-updates-in-dotnet-8-preview-4/#streaming-rendering-with-blazor-components
Steps To Reproduce
<script src="_framework/blazor.web.js" suppress-error="BL9992"></script>
@attribute [StreamRendering(true)]
When you run the page, you initially see the Loading, but than the screen goes blank and you get the error in developer tools.
Exceptions (if any)
Error in Developer Tools
.NET Version
8.0.100-preview.4.23260.5
Anything else?
Visual Studio Enterprise 2022 (64-bit) Preview Version 17.7.0 Preview 1.0
The text was updated successfully, but these errors were encountered: