compareNode return value is wrong in Range.idl & impls

RESOLVED FIXED

Status

()

Core
DOM: Core & HTML
P3
normal
RESOLVED FIXED
18 years ago
5 years ago

People

(Reporter: Heikki Toivonen (remove -bugzilla when emailing directly), Assigned: Heikki Toivonen (remove -bugzilla when emailing directly))

Tracking

({arch})

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nsbeta3+])

The compareNode return value is wrong in Range.idl. Or actually, right now the
IDL file is correct, but the implementation(s) return value is different. It
compiles because DOM IDL is not part of normal build. Once me or Saari checks in
joki's patch, the Range.idl will also contain the wrong return value. This bug
is here to make sure that we will eventually fix the return value in all cases.

Is there a bug for enabling DOM IDL build by default? If we could enable it by
default on at least some platforms we would have noticed this kind of thing
earlier...

I do not think compareNode is part of any DOM level spec, but I put this into
DOM 2 component.
Architecture issue. There are quite a few places that need to be changed, but it
is a simple thing, changing PRInt16 to PRUint16 (and making sure we don't break
anything by doing this).

Nominating for nsbeta3.
Status: NEW → ASSIGNED
Keywords: arch, correctness, nsbeta3
Adding Chris to CC.

Comment 3

18 years ago
Marking nsbeta3+
Whiteboard: [nsbeta3+]
Seems like Chris fixed this already in the big landing. Marking fixed.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Component: DOM Level 2 → DOM Traversal-Range
Component: DOM: Traversal-Range → DOM: Core & HTML
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.