-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Closed
Labels
arch-wasmWebAssembly architectureWebAssembly architecturearea-System.Runtime.InteropServices.JavaScriptos-browserBrowser variant of arch-wasmBrowser variant of arch-wasm
Milestone
Description
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
I'm not sure that this can be considered a "bug" in Blazor (most likely Safari), but it seems primarily like strange behaviour.
When using Safari, there are no initialisation messages logged to the console.
The assetsCache.ts code uses console.groupCollapsed which is supported in Safari, so it's almost like some form of environment detection is failing, yet it's only using typeof (window) === "object" so I'm not sure how that's possible.
Expected Behavior
A message, similar to the following, printed to the browser console.
assetsCache.ts:30
dotnet Loaded 11.21 MB resources
This application was built with linking (tree shaking) disabled.
Published applications will be significantly smaller if you install wasm-tools workload. See also https://aka.ms/dotnet-wasm-features
Steps To Reproduce
Open any Blazor WASM app in Safari.
Exceptions (if any)
No response
.NET Version
8.0.100-rc.2.23502.2
Anything else?
No response
Metadata
Metadata
Assignees
Labels
arch-wasmWebAssembly architectureWebAssembly architecturearea-System.Runtime.InteropServices.JavaScriptos-browserBrowser variant of arch-wasmBrowser variant of arch-wasm