angular.equals(a, b) != angular.equals(b, a) where a = {} && b = {x:undefined}

[noreal81]

Parameter ordering is affecting the output of angular.equals when there are undefined, but present, properties on one of the objects.

a = {};
b = {x:undefined};
angular.equals(a, b) == angular.equals(b, a) // returns false.

http://jsfiddle.net/YCDRx/3/

It appears that this is not fixed between 1.0.2 and HEAD.