Js initialization in OnAfterRender stopped working with 0.7.0

[fs86]

After I upgraded to Blazor 0.7.0 I noticed that initialization scripts of 3rd party JavaScript libraries which I usually call in OnAfterRender stopped working.
E.g. I use select2 (https://github.com/select2/select2) to apply a custom style for my select fields. But it seems like something has changed with Blazor 0.7.0, because the following code (which used to work in 0.6.0) dosn't work anymore:

protected override void OnAfterRender()
{
  base.OnAfterRender();
  JsInterop.InitializeSelect2();
}

My JavaScript function:

window.JsFunctions = {
  initializeSelect2: function() {
    $('select').select2();
  }
}

The control style will get applied when I call StateHasChanged() after JsInterop.InitializeSelect2(), but this will end up in an endless loop. Is there a better place to call InitializeSelect2() than OnAfterRender?

Edit:
I found the following statement about lifecycle methods in the official documentation:

OnAfterRenderAsync and OnAfterRender are called each time after a component has finished rendering. Element and component references are populated at this point. Use this stage to perform additional initialization steps using the rendered content, such as activating third-party JavaScript libraries that operate on the rendered DOM elements.

After doing a bit of research I can say that the corresponding field is not accessible in OnAfterRender.

[grahamehorner]

@fs86 I have also seen this issue when using 0.7.0 where the overridden OnAfterRender is not getting fired,

[grahamehorner]

@fs86 looks like there are is a lot of refactoring happening at present, check out
https://github.com/aspnet/Blazor/blob/master/test/testapps/BasicTestApp/InteropComponent.cshtml

[fs86]

@fs86 I have also seen this issue when using 0.7.0 where the overridden OnAfterRender is not getting fired,

It is getting fired but DOM elements are not accessible in OnAfterRender. I think it might be possible that the event is getting fired too early.

[aweFalafelApps]

Anyone happen to have a workaround for this while we wait for it to hopefully be fixed in 0.8.0?

[Lupusa87]

I am not sure this will be workaround for this case, but you can try.

Please follow timer2 in code

Idea here is to delay some method call.

In my case I used this trick because calling my method inside OnAfterRender was doing nothing, but from timer callback it is working as expected.

Hope it helps.

[mkArtakMSFT]

Closing this as this is definitely working now. Please check out a recent release and if you would experience the same issue feel free to file a new issue.