search

SteveSandersonMS / BlazorInputFile

A file input component for Blazor applications
250 stars 75 forks source link

No file selected message stays right to the button, even after file has been selected ... #38

Open thomiel opened 4 years ago

thomiel commented 4 years ago

... following your blog post https://blog.stevensanderson.com/2019/09/13/blazor-inputfile/

using Blazor wasm .NET 3.1

astevens8182 commented 4 years ago

I am also having the same issue, I had it working and then all of a sudden it stopped. I did not change any code related to the input component as far as I can remember

craigbrown commented 4 years ago

I'm having this issue too with Server-Side Blazor in .NET Core 3.1 (in Chrome)

LaurenceFrost commented 4 years ago

I have the same issue. Server Side Blazor, Chrome, and using v0.2.0. This issue was not there in 0.1.0-preview-00002. It has only started happening since 0.2.0.

Other than the "No file selected" message, the component seems to function correctly.

Hopefully this information is useful.

marinasundstrom commented 4 years ago

I experience the same problem.

craigbrown commented 4 years ago

It looks like this bug was introduced in pull request #23 if that helps.

astevens8182 commented 4 years ago

I have recently found out that the bug no longer exists when I deployed my site to Azure it only seems to be happening in debug

RayKoopa commented 4 years ago

Still happens to me, 0.2.0, .NET Core 3.1 in Edge-Chromium 83

frankfhoch commented 4 years ago

Still happening to me as well. Also in Release (and also deployed on Azure).

sdtperera commented 3 years ago

I'm experiencing the same problem. Even on Azure. Some files are accepted some arent. Not surer whether it hapens when saving image as string;

craigbrown commented 3 years ago

You can work around this by changing the package version to 0.1.0-preview-00002, using CSS to remove the "No file selected" prompt and creating your own one, or if you're using .NET 5 you can just use the built-in InputFile component instead of this one.

Since it is now built in to the framework I doubt there will be any more updates to this package.