Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System.IO.Compression.Brotli not supported on Blazor webassembly, Can we support System.IO.Compression.Brotli #91279

Open
1 task done
Xyncgas opened this issue Aug 29, 2023 · 6 comments
Labels
Milestone

Comments

@Xyncgas
Copy link

Xyncgas commented Aug 29, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

dotnet/aspnetcore#49276
System.IO.Compression.Brotli not supported on Blazor webassembly

Describe the solution you'd like

Can we support System.IO.Compression.Brotli

Additional context

No response

@mkArtakMSFT mkArtakMSFT transferred this issue from dotnet/aspnetcore Aug 29, 2023
@mkArtakMSFT mkArtakMSFT added the arch-wasm WebAssembly architecture label Aug 29, 2023
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Aug 29, 2023
@ghost
Copy link

ghost commented Aug 29, 2023

Tagging subscribers to this area: @dotnet/area-system-io-compression
See info in area-owners.md if you want to be subscribed.

Issue Details

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

dotnet/aspnetcore#49276
System.IO.Compression.Brotli not supported on Blazor webassembly

Describe the solution you'd like

Can we support System.IO.Compression.Brotli

Additional context

No response

Author: Xyncgas
Assignees: -
Labels:

arch-wasm, area-System.IO.Compression, untriaged

Milestone: -

@ghost
Copy link

ghost commented Aug 29, 2023

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

dotnet/aspnetcore#49276
System.IO.Compression.Brotli not supported on Blazor webassembly

Describe the solution you'd like

Can we support System.IO.Compression.Brotli

Additional context

No response

Author: Xyncgas
Assignees: -
Labels:

arch-wasm

Milestone: -

@lewing
Copy link
Member

lewing commented Aug 29, 2023

We left brotli out initially because there is relatively large unmanged component and it is available in the browser directly. We could in theory make it work now when the workload is installed without increasing the default size.

@lewing lewing removed the untriaged New issue has not been triaged by the area owner label Aug 29, 2023
@lewing lewing added this to the Future milestone Aug 29, 2023
@lewing
Copy link
Member

lewing commented Aug 29, 2023

@Xyncgas can you explain your use case so we can help prioritize this issue?

@Xyncgas
Copy link
Author

Xyncgas commented Aug 30, 2023

I can use brotli in browser by sending bytes to javascript and as you know there's a bunch way in javascript to eat brotli, alternatively I can just write brotli myself or install a 3rd party library or I can simply not use brotli

So I don't really... well actually I have an app, that works on MAUI.Blazor but not blazor webassembly, so I used brotli, now I want to put it on the web, you know how MAUI and the browser are all cross platform technology, I should be able to use brotli and it's now the moment for me to decide the compression algorithm otherwise after I release the application everyone's data would break if I change the algorithm but don't worry about it

I simply wanted for .NET to give me brotli so I don't have to grab it somewhere or not use it

@lyellick
Copy link

lyellick commented Sep 7, 2023

+1 for this issue. thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants