Add a test to verify that properties on DOMWindow objects are found before properties of the child frame, and that IDL properties defined in the prototype are found before named document elements. This tests an error that Chromium had at one point, which led to a site compatibility issue on www.multimap.com.
Created attachment 27980 [details] New test, resource file, helper function, and result Either there's something I don't understand about eval, or a trunk build currently fails some of these checks. window.defaultStatus, window.status, and window.name are modified when the subframe or input element changes: they go from undefined to '' (empty strings). It's still worth adding this test to detect other regressions.
Created attachment 27981 [details] Same patch; added missing newline to end of window-properties.js.
Comment on attachment 27981 [details] Same patch; added missing newline to end of window-properties.js. LGTM
I made a small change to remove the dependency on the test file location for win['Location'], then landed as r41672.
Test is failing because of differences in window size and location (outerHeight, outerWidth, screenTop, and screenX).
Created attachment 28655 [details] Remove dependency on numerical values The exact values of these numbers are not pertinent to this test, only that they are unchanged.
Fix reviewed by dglazkov on IRC, landed as r41736.
I'm surprised by the use of toLowerCase on the result of typeof. That string should reliably be the same constant across multiple JavaScript engines and there's no reason to call toLowerCase.
Comment on attachment 28655 [details] Remove dependency on numerical values Clearing review flag, as this was landed already.
Created attachment 29199 [details] remove unnecessary toLower
Comment on attachment 29199 [details] remove unnecessary toLower r=me
Cleanup landed in r42176.