BitFileUpload - add a property to gain access to the BrowserFile instance

[nhwilly]

Not sure if this is even possible, but I am using the BrowserFile instance returned by the InputFile control to get access to the bytes so that I can feed them into an image cropping component. This is all happening client side, so that I am never sending the original document to the server. I need to crop it first, then send it when they are finished.

I have cobbled something together with a <label for...> and invisibile <InputFile> approach, but it's not nearly as cool as yours. I did have to expand the SignalR circuit size to get it to work with Server rendering, but it's pretty reliable.

builder.Services.AddServerSideBlazor() .AddHubOptions(options => { options.MaximumReceiveMessageSize = 16 * 1024 * 1024; // 16MB });

BitFileUpload does not permit access (if it even has it) to the BrowserFile, which means I can't use it for my feature.

This is a "wouldn't it be cool" feature, since I already have something working.

Just thought I would leave it here.

Thank you for considering.

[github-actions[bot]]

Hello there! I'm a wiki 🤖.

Based on the content of this thread, I've found a potentially relevant wiki page for you!

✨ View Wiki Page

I hope this helps!

[msynk]

@nhwilly Thanks for contacting us.
The BitFileUpload is specifically designed and developed to Upload files not anything else. we had a plan to develop another component named BitFileInput in the past, but we discard it since it wasn't that useful at the time.

[msynk]

I suggest you file a new issue to add a new component for your need. we will see if we can develop such a component in the coming weeks.

[nhwilly]

I won't have my PC until the end of the year. But I'll post something then. Thank you.