http://stackoverflow.com/questions/7895359/dojo-io-iframe-send-file-upload-sends-get-request-in-ie8

The Flash uploader in IE8 doesn’t seem to do anything when I set the URL parameter programmatically after creation, so I am setting it to a fixed value on creation and then setting the name parameter in programmatically after creation. It looks like I can then parse the POST on the server side to handle the fact that the POST is coming into the wrong place (obviosuly I can’t do a redirect because a POST redirects to a GET). Hopeful, but not yet got this working

You’re a good man.

The uploader button can be clicked when it is created declaratively but not programmatically. The problem comes in at around 1.7.0b5 and it looks like it associated with a change in the button css.

I’m still trying to call onSubmit programmatically. I have taken the uploader code from 1.7.0b1 into a 1.7.1 (I can’t use 1.7.0b1 directly because of other bugs) and it looks like the 1.7.0b1 Uploader can be clicked OK. With my patched-up release I can now call the onSubmit properly in Firefox. However I run into another very strange bug when I call the onSubmit from IE. It fires up an upload dialog in IE. I’m still investigating this one.

I’m in Europe so it’s late, but if you make any progress please post.

Thanks,

Mike

It’s me again (you’ll see my comments some months back). I never got the new Uploader onsubmit working programmatically by patching 1.6.1, but now I am moving on to using the 1.7.1 and I’ve hit more problems.

Consider the following whihc should create two upload/submit button pairs – one declaratively and one programmatically. In 1.6.1 in both firefox and IE they both are created and they both pop up dialogs. In 1.7.1 in both firefox and IE you get both pairs of buttons, but the second one doesn’t pop up a dialog when you click it.

Unfortunately I need to create the buttons programmatically inside a dialog.

Any help appreciated.

Mike

Vulnerability Risk Manager

dojo.require(“dojox.form.Uploader”);
dojo.require(“dojox.form.uploader.plugins.IFrame”);
dojo.require(“dijit.form.Form”);
dojo.require(“dijit.Dialog”);
dojo.addOnLoad(function(){

var form = new dijit.form.Form({
method:”POST”,
action:”scanner/uploadJson?id=2″,
id:”myForm2″,
encType:”multipart/form-data”
});
var uploader = new dojox.form.Uploader({
name:”uploadedfile”,
multiple:”true”,
label:”Select Some more Files”
});
var submitter = new dijit.form.Button({
type:”submit”,
label:”submit more”
});
dojo.connect(form, “onSubmit”, uploader, function(e) {
e.preventDefault();
this.upload();

})
form.domNode.appendChild(uploader.domNode);
form.domNode.appendChild(submitter.domNode);
dojo.byId(“secondForm”).appendChild(form.domNode);
})

Great article!
I’ve tried this on several different browsers just to find out it didn’t work on all except IE9 (!)
After switching to Dojo 1.7 it worked. There were however so many different other problems with 1.7 I’ve decided to go back to 1.6 (for now) until I’ll find the time to get a grip on the specific changes in 1.7. I suspect my use of the Zend Framework has some influence on this behaviour.

Just a couple of things…

You mention “Ever added the forEach method to Arrays?”, but this is a part of JavaScript since version 1.6 (https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Array/forEach). I happen to know because I recently wrote a post about that :) (http://www.bjelic.net/2011/11/16/coding/evolution-of-javascript-loop/)

Another thing is that you probably meant to write “Context is the key differentiator between JavaScript and all OTHER major languages.” ;)

Cool article!
Cheers,
Bojan