[XML-SIG] Documenting DOM bugs

[Andrew Clover]

Uche Ogbuji <uche.ogbuji at fourthought.com> wrote:

> Do you have a moment to comment on your testing mthodology, and perhaps even 
> to ost the scripts you used?

No scripts I'm afraid! My testing methodology is to see whether my DOM apps
work with an implementation, and if not find out why not and which other
versions have the same behaviour. I didn't set out to document bugs, just
get my stuff working. ;-)

> It feels as if you have a lot more goodies than just this comprehnsive
> table.

Not so much; I know there are a fair few problems with DTD-related features,
but haven't investigated too hard as I don't really necessarily except a DOM
to provide them (especially given the limited and occasionally woolly spec
wording in this area). I've seen a few serialisation issues too but that
doesn't concern me enough to check up on, as I'm not using it (and it's not
a Core feature anyway).

> changing [Attr's] children puts the DOM into an inconsistent state.

> This sounds like a current bug.  Could you check a repro case into the
> tracker?

Sure. (#754713)

> I don't expect us to ever have live return from getElementsByTagName or the 
> NodeIterator interfaces.

OK. I had kind of expected this for an imp like minidom, but 4DOM was a
surprise - can this be clearly documented somewhere?

cheers,

-- 
Andrew Clover
mailto:and at doxdesk.com
http://www.doxdesk.com/