This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The test DOM-Core-Level1 hc_entitiessetnameditem1 tries to catch two types of exception. This turns into the following Javascript code: if (ex.prototype.HasOwnProperty('code')) { switch(ex.code) { ... } } The problem is that HasOwnProperty only works in IE (I guess), the proper capitalization is hasOwnProperty. It also looks like neither Mozilla nor Konqueror support ex.prototype (specifically on exceptions) at the moment, but I'll fix that for Konqueror, and maybe it's fixed in a more recent Mozilla version. But anyway, I'm not sure why this is needed - why not test for ex.code right away? Isn't ex.code mandatory to support?
In fact, this test requires that the 'code' is stored in the prototype of the exception, instead of being stored in the exception itself. Is there any reason for this requirement? There isn't much point in having one prototype per DOM exception code, the memory footprint is much smaller with a single error prototype for all errors, and the code stored into it. Can the test be removed altogether? Thanks.
oops, when I said "the test" I meant the if() test, not the whole .xml file :)
to curt.
Fixed by bug 515