UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
1. assign a positive integer properties to an object that is at or above 1024
2. assign a negative integer property to the object
3. attempt to use hasOwnProperty() to test for the negative integer property

What is the expected behavior?
What used to happen is that referencing the property using a negative number, rather than a string, used to work.

What went wrong?
For some reason, setting an integer property that is at or above 1024 seems to damage the ability to test for subsequent negative integer properties using a number. The property test seems to work using a string.

var o = {};
o[1024] = true;
o[-1] = true;
o.hasOwnProperty(-1) results in false
o.hasOwnProperty('-1') results in true

If you use 1023 instead of 1024, things work as before. The break point seems to be 1024.

Did this work before? Yes 54.0.2840.99

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0