> Looks like it's been fixed in ES5

That was published 9 years ago.