When validation is set in order prevent a user from uploading an unsupported file, it works fine when the user uploads files with extensions.

The problem is, if the same user attempts to upload from a mobile device such as from google drive, the file typically has no extensions, and therefore it fails validation; even though it in fact is a supported file.

Somehow, when we know it's a mobile device, tablet, or a MAC we need to be able to allow no extensions.

Create an option or detect if it is be accessed from a mobile device, and allow us to choose if we want allow files to have no extensions, even if the validation is active so that if a file is uploaded without an extension in those cases it doesn't trigger the validation and fails clients side.

Please implement file filtering on the Open Dialog Window via the accepts property of the rendered HTML 5 input file control. 

The current implementation provides file filtering via flash or silverlight but this functionality is built into the <input type="file"/> control by adding the accepts property. In order to provide file filtering for all modern browsers, without using plugins, the accepts property would only need to be added to the already rendered file control. <input type="file" accepts="image/jpeg, image/gif" />

I have made this change via developer tools in each major browser and it worked fine across the HTML 5 compliant browsers (FF, Chrome, IE).

Upgrading to UI for ASP.NET AJAX Q2 2015 (2015.2.729.45) sets requestLimits maxAllowedContentLength in web.config to 

<requestLimits maxAllowedContentLength="0" /> <!--8MB Max upload-->

resulting in errors like "PRM_ServerError" on postbacks.

when deleting files from radasyncupload via the "built-in" delete button, "get_fileName()" method in both the upload_removing and upload_removed events returns correct data. However, when deleting files via the api, the get_fileName() method returns bad content.

built-in button something like:
document.pdf

api something like:
document.pdf<span class="ruFileProgressWrap"><span class="ruFileProgress"></span></span>

to reproduce: 
1. run attached web form. select file for upload. click remove button. view console. all good.

2. click the "delete via api" checkbox to enable. select another file. view console. bad.

when deleting files from radasyncupload via the "built-in" delete button, both the upload_removing and upload_removed events are fired. However, when deleting files via the api, only the uploadRemoved event is fired.

to reproduce: 
1. run attached web form. select file for upload. click remove button. view console. note console entries have text "filename in UPloadRemoving.." as well as "filename in UploadRemoved...". Good

2. click the "delete via api" checkbox to enable. select another file. view console. Note console entry only has text "filename in UploadRemoved..." bad.

when files are deleted via the user interface, this "frees up" the max file count for additional files to be uploaded. When files are deleted via API, the deleted files are still counted against the maxfilecount, and are not "freed up"

to reproduce:
run the attached web form.
do not select "delete via api" checkbox
add and remove a number of files.
good.

reload.
do not select "delete via api"
upload file A
select "delete via api"
upload file A one more time (note it will be deleted via api before it actually gets uploaded)
deselect "delete via api"
upload file B
note you can no longer upload files, allthough only 2 have been uploaded and maxfilecoutn is 3
bad.