dojo.safeMixin can fail in IE

[dhaber]

This applies to dojo 1.4 through 1.6 and IE 6, 7 & 8.

If you declare a new class that has a constructor which uses dojo.safeMixin but you pass no parameters to the constructor it will fail in IE. For example:

dojo.declare("a.b.c", null, {
	
	constructor: function(args) {
		dojo.safeMixin(this, args);
	}});

The above will fail in IE if you do this:

var d = new a.b.c();

[bill]

Seems like this ticket is invalid. You are calling

dojo.safeMixin({}, undefined)

whereas the API documentation says that you have to pass in an object as the second argument.

[dante]

Techincally invalid by API docs. dojo.mixin({}, undefined) works fine. Ironic the mixin() with the word "safe" in it doesn't check presence like the seemingly "unsafe" mixin() (and private _mixin() functions) attached to the dojo object.

[acabler]

I would really like to see a fix for this. This one just cost me a day and is very difficult to debug, but very easy to fix. If nothing else, it would be nice to have the behavior match across the browsers. Especially since IE bugs are much harder to debug.

[bill]

Giving to Eugene since safeMixin() is defined in declare.js.

[soleimani]

a simple workaround is always pass {} to declare function

    var jr = new JsonRest(); // cause exception
    var jr = new JsonRest({}); // it works

[dylan]

Given that no one has shown interest in creating a patch in the past 4+ years, I'm closing this as patchwelcome.