The test assumes a fixed list of properties on the global object


The test checks the property names of the global object against the following list:
["eval", "parseInt", "parseFloat", "isNaN", "isFinite", "decodeURI", "decodeURIComponent", "encodeURIComponent", "escape", "unescape", "NaN", "Infinity", "undefined"]
This test has two problems:
  1. The list above is missing quite a few standard properties (e.g. "encodeURI", "Array", "JSON", "Math", etc)
  2. Implementations are allowed to extend the global object and many do (including all the major browsers).


paulbartrum wrote Aug 17, 2010 at 1:06 AM

The same problems apply to all the tests through

paulbartrum wrote Aug 17, 2010 at 1:09 AM

One possible fix would be to check that the returned array is a superset of the hard-coded array (rather than an exact match, which is what is happening now).

paulbartrum wrote Aug 18, 2010 at 5:37 AM

Duplicate of #26847

jwalden wrote Jan 1, 2011 at 9:58 PM

I fixed the subsetting issue awhile ago, but the "incomplete properties" complaint is still valid.

wrote Feb 13, 2013 at 2:09 AM