You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When investigating to set the title via prerendering and also via client side ideally using the same "mechanism", I see solutions that use JsInterop for client-side and parse the html for prerendering. I don't like any of that.
I was wondering if there are any plans or drafts about how Blazor will tackle this?
I thought that having some method that instantiate App component we can then access the router or some title component to use it for prerendering, while also using for client-side.
If we do that, we may actually extend to have a Head section entirely or generic "sections" aka Razor, and Host.cshtml will be as simple as doing:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When investigating to set the title via prerendering and also via client side ideally using the same "mechanism", I see solutions that use JsInterop for client-side and parse the html for prerendering. I don't like any of that.
I was wondering if there are any plans or drafts about how Blazor will tackle this?
I thought that having some method that instantiate
App
component we can then access the router or some title component to use it for prerendering, while also using for client-side.If we do that, we may actually extend to have a Head section entirely or generic "sections" aka Razor, and
Host.cshtml
will be as simple as doing:Accessing those properties via client-side will also help add/remove static dependencies from Lazy Loaded components.
Is any of this make sense? is there any plans for such featur(es) ?
Beta Was this translation helpful? Give feedback.
All reactions