Hi IG team,
The igUpload component starts out as a button and only renders the "ui-iguploadsingle" widget after the first upload has been initialized.For our purposes this causes an inconsistent layout and user experience. So I was wondering is there is a way to have the uploader expanded to its full size by default.You check out this behavior on your demo page https://www.igniteui.com/file-upload/basic-usageJust start uploading a file and immediately cancel. Now you have the expanded view without any files uploaded.
Collapsed:
Full:
Hi,
Thank you for contacting Infragistics Developer Support.
You can achieve what you are looking for by getting the file input the upload is using and calling its change method. This will make the upload think that you uploaded a file and you will get the larger container. Note that because we don’t provide an actual file, a client side error will be thrown by the upload and you should make sure that you don’t handle it with your normal error handling logic, since this error is expected. In addition, you can hide what you are doing from the end user, by initially hiding the upload and only showing it once the client side error has happened.
Please check the attached sample for one possible way to do this.
Please let me know if you have any additional questions.
Regards, Dimitar Software Developer www.infragistics.com
file input test.zip
Hi Dimitar,I just noticed this solution does not work when the "allowedExtensions" property is set.Do you have any ideas on how to get that to work?
If you want an official solution, I would suggest logging a product idea in our product ideas site.
Submitting your idea will allow you to communicate directly with our product management team, track the progress of your idea at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you.
Remember when submitting your idea to explain the context in which a feature would be used and why it is needed as well as anything that would prevent you from accomplishing this today. You can even add screenshots to build a stronger case. Remember that for your suggestion to be successful, you need other members of the community to vote for it. You can also link back to this thread for additional details.
Thank you in advance to submitting your product idea.
I found a workaround by setting the allowedExtensions in fp.change().after().This is not ideal because I was using MVC helpers for the extensions before, an official solution to this would be nice.