Open danielchalmers opened 1 week ago
I don't think we're using the code wrong but we might have missed something https://github.com/search?q=repo%3AMudBlazor%2FMudBlazor%20cookie&type=code
I don't think we're using the code wrong but we might have missed something https://github.com/search?q=repo%3AMudBlazor%2FMudBlazor%20cookie&type=code
Better to redirect to PR that introduced it: https://github.com/MudBlazor/MudBlazor/pull/8602
https://github.com/BytexDigital/BytexDigital.Blazor.Components.CookieConsent/pull/31 would atleast fix the .js file from not being loaded, but the .wasm file is a bit tricky to me at the moment, as it gets baked into the bootup process of the WASM environment and I'm not sure yet how to best combat the blocking of this file crashing the entire bootup. I'll look around a little
31 would atleast fix the .js file from not being loaded, but the .wasm file is a bit tricky to me at the moment, as it gets baked into the bootup process of the WASM environment and I'm not sure yet how to best combat the blocking of this file crashing the entire bootup. I'll look around a little
As far as I read about the Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
error on StackOverflow, it seems like the adblocker is blocking URLs that contain "cookieconsent" or similar terms. While issue #31 can deal with the JS block since you can customize that part, there is nothing you can do about the assembly name.
It's not really impossible to dynamically load an assembly in WASM, but it is not trivial, especially if you need to rename the original assembly. Furthermore, it is impossible to dynamically load it if you are using WasmEnableWebcil
since, as far as I know, the AssemblyLoadContext
doesn't support it (though I am uncertain about this, as I recall some complaints about it in the runtime repository). At this point, it would be easier to fork the library and apply the AssemblyName
tag change in the csproj
.
The assembly load problem is the nastiest one because it will cause your website to crash, while a failed JS load won't, and the website will continue functioning.
Loading mudblazor.com in incognito with uBlock cookie filters enabled on the latest version results in the site getting stuck on the loading screen with these errors:
If I disable the adblock, load the site successfully, then turn it back on, I get this error:
but the site still loads ok.
I'm looking to be able to take them blocking the cookies as a denial and continue loading the site smoothly.