Add log about browser tab sleeping

[BrennanConroy]

In reaction to #33970

Added the freeze event handler log. (Thanks Sourabh)

[pranavkm]

@BrennanConroy does this also affect Blazor? (FYI @SteveSandersonMS)

[BrennanConroy]

I assume you're still using the SignalR typescript client, so yes :)

[lewing]

cc @kg @pavelsavara

[kg]

I think we should definitely integrate this, but it's unfortunate that Firefox doesn't support it. On the other hand, FF is less aggressive about pausing than Chrome right now.
Do we know what kind of caveats there are for this? Is Chrome likely to punish us for using it the way we intend to?

[BrennanConroy]

Do we know what kind of caveats there are for this?

Other than the obvious ones like potential deadlocking if you use multiple locks and that the feature is experimental, I don't know of any caveats.

Is Chrome likely to punish us for using it the way we intend to?

No idea, I briefly talked to the Edge team and they didn't say not to use it, and that the heuristics they use probably wont remove WebLocks.

[davidfowl]

I don't think this is a good idea. I can't articulate why as yet, but my Spidey sense tells me that this is a bad idea.

[kg]

Note that from what I can tell from reading the relevant docs, this will only prevent the tab from being put to sleep (i.e. fully unloaded), and won't necessarily stop timers from being throttled down to a lower frequency. It's still worthwhile to avoid having the tab go to sleep either way. One thing is that there are some applications that probably won't want to have a WebLock active while they're waiting for things to happen, while other apps do want it. We may need to find a way to have the application author signal this.

[BrennanConroy]

Another option is we don't make any code changes and document how users can workaround the sleeping tabs issue in their own code.

Although, I would then keep the freeze event listener and potentially add a note about the docs.

[bradygaster]

i like @BrennanConroy's suggestion. If @davidfowl (and @shirhatti) are iffy on this approach, let's wait and doc it.

[davidfowl]

I much prefer the documentation suggestion rather than baking this into our library. We'll learn about the warts in a way that's possible for customers to work around.

[kg]

Users are significantly inconvenienced by the current state of things, and it's possible for us to mitigate it through some library changes, but I agree that it's not necessarily right to bake in web locks.

[BrennanConroy]

Updated to just be a log

[BrennanConroy]

Ping, look at dotnet/AspNetCore.Docs#22773 too

[halter73]

I was trying to understand the old comments and then I realized this used to be the WebLock PR 😄.

[samuelwine]

@BrennanConroy Please forgive me if this is the wrong place to ask...
I have a WebView within a Maui app, which displays my website which uses the javascript SignalR client library. I've been trying to use a weblock (as suggested in the docs) to keep the tab unfrozen, but this hasn't helped. Would it make sense that a WebView could be different in this respect than a regular browser tab?
Thank you

[ghost]

Hi @samuelwine. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.