Blazor Web App (.net 8): javascript not executed on page change

DOM manipulation

The first thing to note with your code is that you are doing a lot of DOM manipulation with jQuery. You should try to do as much of your DOM manipulation from within Blazor as you can. The main reason is that Blazor manages the DOM based on the state of your components, so any changes you make outside of Blazor could be lost when the state changes in your Blazor components.

Relevant StackOverflow post: Blazor, doubts regarding modifying DOM from JavaScript

Blazor page loading

Blazor isn't like a traditional server rendered app. Regardless of which flavour of Blazor you are using (server / web assembly), you only load resources (e.g. JS, CSS) on the initial page load, much like any other SPA. This means that your JS will only run on the initial load - future navigations are made within the context of the original request.

As you are experiencing, JS will not automatically run per-navigation unless you specifically invoke it.

How to invoke JS from Blazor

Regardless of your strategy for invoking JS per-navigation, you need to understand how to call JS from your Blazor code.

Luckily Blazor gives us an easy way to do this.

Set up the javascript methods you want to run from Blazor.

(function() {
  function sayHello(name) {
    console.log(`Hello, ${name}!`);
  }

  // Create a namespace within the global scope that you can
  // add your own functions to.
  // You can only call JS functions from Blazor that are 
  // in the global scope
  window.myNamespace = window.myNamespace || {};
  // Add your function(s) to your scope here.
  // You may want to split different functions into different
  // files - hence why you get or create your namespace first.
  window.myNamespace.onLoad = {
    sayHello: sayHello
  };
)();

Call the JS function from a Blazor component. Blazor can only start interacting with JS after the first render. You can pass 0 or more arguments from Blazor into your JS function (including references to DOM elements, using the @ref Blazor binding).

@inject IJSRuntime JSRuntime
@code {
  protected override async Task OnAfterRenderAsync(bool firstRender)
  {
    if (firstRender)
    {
      // call the JS function
      // note how we don't need to explicitly call window.myNamespace
      await JSRuntime.InvokeVoidAsync("myNamespace.onLoad.sayHello", "World");
    }
  }
}

How to invoke JS on every page load

There are several approaches you could take here. One approach I might use would be to have a base component for your pages that can call the required functions on the first render.

This would mean that you have to remember to inherit from the base class when you create a new page.

Set up your base page component:

public abstract class BasePageComponent : ComponentBase
{

  [Inject]
  protected IJSRuntime JSRuntime {get; set;}

  protected override async Task OnAfterRenderAsync(bool firstRender)
  {
    await base.OnAfterRenderAsync(firstRender);

    if (firstRender)
    {
      // run some JS function(s) here 
      await JSRuntime.InvokeVoidAsync("myNamespace.onLoad.sayHello", "World");
    }
  }
}

Simply set up your pages to inherit from this base class like so:

@page "/"
@inherits BasePageComponent

There are undoubtedly other ways in which you could run JS per-navigation. My answer will at least arm you with the ability to call JS from Blazor on page load, and should hopefully inspire you to re-think your current reliance on jQuery.