I think Firefox is putting out automatic updates too fast and releasing buggy versions myself.

This is an odd one that I have not been able to figure out a "good" solution for, but with some experimenting I found that by adding this in the css:

.fileupload embed { background-color:inherit !important; padding:9px 9px 9px 9px; }

the button is partially visible but still has a white line through it and for it to work you have to click right on the white line part of the button because that is the actual flash object. It just seems the flash object itself is white in Firefox obscuring the button which should show through it like in other browsers.

Wish I had a better solution but at the moment I don't and the above fix doesn't seem to have any negative side effects in other browsers.

Best,

Joe

Hi Joe,

To be honest since the original developer of NeatUpload stopped supporting it in May of 2010 and I don't really feel capable of fixing the problem or maintaining it long term, I'm leaning towards removing NeatUpload from the next release of mojoPortal and investigate using the Ajax file upload from the ajaxcontroltoolkit. 

Best,

Joe

I think NeatUpload is using an older version of swfupload, which itself is no longer actively developed. Updating NeatUpload to even the last update of swfupload might fix it but would be significant work requiring changes in NeatUploads C# code and the generated javascript produced by it which also would require a deep understanding of how NeatUpload really works.

Since the progress bar is really the only key advantage of NeatUpload and since the ajax file uploader does show progress in modern html 5 browsers it seems promising as a go forward plan. I just need to implement it in one feature first as proof of concept to make sure it doesn't require page methods and can be used inside UserControls where page methods cannot be used. 

Getting rid of NeatUpload wouild also mean we no longer need different web.config for medium trust which would be nice and the ajax uploader progress bar would work even in medium trust as long as the browser supports it where we currently cannot use NeatUpload.

Looks like I'll have to rule out the ajaxcontroltoolkit AjaxFileUploader. It looked promising but in trying to integrate it in the Shared Files feature I encountered several limitations that I could not solve.

1. if you have more than one on a page only the first one works. ie if I put 2 instances of Shared Files on a page and try to upload in the bottom one the file is uploaded in the top one
2. the state of other controls is not available at all in the file upload postback so it was impossible to upload a file in a folder within Shared Files because the current folder id could not be obtained. The documentation for it shows a property ContextKeys which supposedly allows you to pass some extra values with the upload but in fact it does not work and was not implemented so the documentation is just wrong. This is verified by google search of others trying to figure out how to make it work and by looking at the actual source code of the uploader it doesn't use the property anywhere.

I'm going to have to look at other options.

Best,

Joe

I'm leaning toward building one with this blueimp one, at the moment but will be doing some prototyping and proof concept before making a final decision. I'm inclined to not use Flash and not worry too much about older browsers in terms of supporting progress bars and multi file selection.

I've also looked at uploadify but only their flash version has a compatible license and I'd rather not use or depend on flash. Their html 5 javascript one has a commercial license that is not compatible.

The fyneworks sounds good reading about it but multi file selection doesn't seem to work for me in Chrome on their example page so I'm not inclined to try working with it.