Less importantly, "hmtlEscape" is a strangely consistent typo.
More importantly, in sth.prototype.report (yeesh, sth? who comes up with these names? ;-) ), in the nested function testline, there are two calls to "this.hmtlEscape" -- but testline is called as "testline(ut)", thus its this object is the global, which does not have a "hmtlEscape" property, and therefore it throws an exception that breaks the harness entirely. Why the harness works at all in IE8 I have no idea; it shouldn't.
http://es5conform.codeplex.com/sourcecontrol/changeset/view/55693?projectName=ES5conform#816017
Less importantly, "hmtlEscape" is a strangely consistent typo.
More importantly, in sth.prototype.report (yeesh, sth? who comes up with these names? ;-) ), in the nested function testline, there are two calls to "this.hmtlEscape" -- but testline is called as "testline(ut)", thus its this object is the global, which does not have a "hmtlEscape" property, and therefore it throws an exception that breaks the harness entirely. Why the harness works at all in IE8 I have no idea; it shouldn't.
Jeff
es5conform.codeplex.com/sourcecontrol/changeset/view/55693?projectName=ES5conform#816017
Less importantly, "hmtlEscape" is a strangely consistent typo.
More importantly, in sth.prototype.report (yeesh, sth? who comes up with these names? ;-) ), in the nested function testline, there are two calls to "this.hmtlEscape" -- but testline is called as "testline(ut)", thus its this object is the global, which does not have a "hmtlEscape" property, and therefore it throws an exception that breaks the harness entirely. Why the harness works at all in IE8 I have no idea; it shouldn't.