aboutsummaryrefslogtreecommitdiffstats
path: root/test/ng/parseSpec.js
diff options
context:
space:
mode:
authorPeter Bacon Darwin2013-10-05 10:49:09 +0100
committerVojta Jina2013-10-07 09:01:13 -0700
commit7a586e5c19f3d1ecc3fefef084ce992072ee7f60 (patch)
tree2690c915adb20d92a065d9ad9d7438766d4620f8 /test/ng/parseSpec.js
parentfb99f542060d3959d273634c90889788861b5c05 (diff)
downloadangular.js-7a586e5c19f3d1ecc3fefef084ce992072ee7f60.tar.bz2
fix(*): protect calls to hasOwnProperty in public API
Objects received from outside AngularJS may have had their `hasOwnProperty` method overridden with something else. In cases where we can do this without incurring a performance penalty we call directly on Object.prototype.hasOwnProperty to ensure that we use the correct method. Also, we have some internal hash objects, where the keys for the map are provided from outside AngularJS. In such cases we either prevent `hasOwnProperty` from being used as a key or provide some other way of preventing our objects from having their `hasOwnProperty` overridden. BREAKING CHANGE: Inputs with name equal to "hasOwnProperty" are not allowed inside form or ngForm directives. Before, inputs whose name was "hasOwnProperty" were quietly ignored and not added to the scope. Now a badname exception is thrown. Using "hasOwnProperty" for an input name would be very unusual and bad practice. Either do not include such an input in a `form` or `ngForm` directive or change the name of the input. Closes #3331
Diffstat (limited to 'test/ng/parseSpec.js')
-rw-r--r--test/ng/parseSpec.js20
1 files changed, 20 insertions, 0 deletions
diff --git a/test/ng/parseSpec.js b/test/ng/parseSpec.js
index 87cc79af..19182332 100644
--- a/test/ng/parseSpec.js
+++ b/test/ng/parseSpec.js
@@ -351,6 +351,26 @@ describe('parser', function() {
expect(scope.$eval('toString()', scope)).toBe('custom toString');
});
+ it('should not break if hasOwnProperty is referenced in an expression', function() {
+ scope.obj = { value: 1};
+ // By evaluating an expression that calls hasOwnProperty, the getterFnCache
+ // will store a property called hasOwnProperty. This is effectively:
+ // getterFnCache['hasOwnProperty'] = null
+ scope.$eval('obj.hasOwnProperty("value")');
+ // If we rely on this property then evaluating any expression will fail
+ // because it is not able to find out if obj.value is there in the cache
+ expect(scope.$eval('obj.value')).toBe(1);
+ });
+
+ it('should not break if the expression is "hasOwnProperty"', function() {
+ scope.fooExp = 'barVal';
+ // By evaluating hasOwnProperty, the $parse cache will store a getter for
+ // the scope's own hasOwnProperty function, which will mess up future cache look ups.
+ // i.e. cache['hasOwnProperty'] = function(scope) { return scope.hasOwnProperty; }
+ scope.$eval('hasOwnProperty');
+ expect(scope.$eval('fooExp')).toBe('barVal');
+ });
+
it('should evaluate grouped expressions', function() {
expect(scope.$eval("(1+2)*3")).toEqual((1+2)*3);
});