Re: [PATCH 0/6] MR7970: mshtml: Misc prop fixes & improvements.

[Jacek Caban (＠jacek)]

Jacek Caban (@jacek) commented about dlls/mshtml/tests/documentmode.js:
>          window.toString.call(null);
>          ok(false, "expected exception calling window.toString with null context");
>      }catch(ex) {}
> -
> -
>    ok(!Object.hasOwnProperty.call(f, "arguments"), "arguments is a prop of createElement");
> -
>    ok(!Object.hasOwnProperty.call(f, "caller"), "caller is a prop of createElement");
> -
>    ok(!Object.hasOwnProperty.call(f, "length"), "length is a prop of createElement");
> }else {
>        ok(Object.getPrototypeOf(f) === Function.prototype, "unexpected document.createElement prototype");
>        e = window.toString.call(null);
>        ok(e === "[object Window]", "window.toString with null context = " + e);
>        e = window.toString.call(external.nullDisp);
>        ok(e === "[object Window]", "window.toString with nullDisp context = " + e);
> -
> -
>    ok(f.hasOwnProperty("arguments"), "arguments not a prop of createElement");
> -
>    ok(!f.hasOwnProperty("length"), "length is a prop of createElement");

For testing exposed properties, using `test_own_props` would be better. Additionally, it would be good to test the actual value of the property (probably `null` in this case).