When you spin up a Blazor app and start navigating between pages you immediately run into an interesting problem.

Although it seems to your users like they’re switching between different pages on a web site, in reality they’re always hitting the same page (index.html for WASM or _Host.cshtml for Server) and Blazor is switching different content ‘on’ and ‘off’ (showing/hiding).

In fact this is how all SPA (single page applications) work.

But what if you want to update the page title from your code?

One of the examples in Blazor by Example has you create a little timer (Pomodoro timer) which counts down from 25 minutes and then uses a little javascript to dynamically show the current value of the timer in the browser’s title…

So how is this achieved?

.NET 3.1

The only way to pull this trick off pre .NET 5 is to use a little javascript.

You can declare the javascript (in index.html if you’re using Blazor WASM or _Host.cshtml if Server):

    window.setTitle = (title) => document.title = title;

Then in your Blazor components, inject the IJSRuntime

@inject IJSRuntime JSRuntime

Before finally invoking the setTitle javascript method from your component…

JSRuntime.InvokeVoidAsync("setTitle", remaining);

.NET 5

Happily this problem is solved with .NET 5 where you can now use dedicated components to achieve the same result.

First you’ll need to add a package reference:

dotnet add package Microsoft.AspNetCore.Components.Web.Extensions

Then include a script reference (in index.html or _Host.cshtml):

<script src="_content/Microsoft.AspNetCore.Components.Web.Extensions/headManager.js"></script>

From here you’re free to use Title, Link and Meta components to set the page’s title, or dynamically add link and meta tags to the HTML head.

@using Microsoft.AspNetCore.Components.Web.Extensions.Head

<Title Value="@remaining"></Title>

@code {
    private string remaining { get;set; }

Pretty handy huh?

Oh, and remember you can move that @using statement to _Imports.razor (to save declaring it in every component).

Build better ASP.NET web applications, faster

I email every week with hints, tips and advice on how to push through all the noise to get your ASP.NET applications built.

Drop your email in the box below and I'll send new articles straight to your inbox.

I respect your email privacy. No spam, unsubscribe anytime with one click.


Next up

Sure, you could write all those Blazor HTTP calls yourself…
Writing boilerplate API client code is deadly dull and repetitive, Refit will do it for you
With so many Blazor Component Libraries, which one is best for you?
There’s no shortage of component libraries available for Blazor, but how do you figure out which one you should use?
Will .NET 6 fix Blazor Prerendering?
Prerendering eradicates Blazor WASM’s initial load time and .NET 6 promises to address its one key limitation