Closed
Bug 6673
Opened 25 years ago
Closed 23 years ago
Need a way to return undefined as value through the JS stubs
Categories
(Core :: DOM: Core & HTML, defect, P2)
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: joki, Assigned: vidur)
Details
(Keywords: dom0)
Properties which should come back undefined in JS currently have to come back
with a value from the native property getters. (i.e. event.screenX for a key
event must be 0, not undefined).
|
Assignee | |
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M7
Moving to DOM Level 0 component. Move to DOM Level 1 if that is more correct.
|
|
Assignee | |
Updated•25 years ago
|
Target Milestone: M7 → M10
|
|
Assignee | |
Comment 2•25 years ago
|
||
Moving to M10.
Target Milestone: M10 → M14
Not a beta issue.
HTML DOM bugs are M11/P2 for Vidur.
|
||
Updated•25 years ago
|
Target Milestone: M11 → M13
|
|
||
Comment 5•25 years ago
|
||
Moving to M13.
|
|
Assignee | |
Comment 6•25 years ago
|
||
In an attempt to get my bug list in order again, marking all the bugs I have
currently as ASSIGNED.
|
|
Assignee | |
Updated•25 years ago
|
Target Milestone: M13 → M17
|
|
Assignee | |
Comment 7•25 years ago
|
||
Quite the unpopular bug, isn't this? I'm moving this forward.
|
||
Comment 8•24 years ago
|
||
This bug has been marked "future" because the original netscape engineer
working on this is over-burdened. If you feel this is an error, that you or
another known resource will be working on this bug,or if it blocks your work
in some way -- please attach your concern to the bug for reconsideration.
Target Milestone: M17 → Future
|
|
Assignee | |
Comment 9•23 years ago
|
||
The generated code was phased out with the XPCDOM landing. I don't believe this
is necessary for compatibility. Marking it WONTFIX.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•