Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
I rescently entered this bug. After talking to vidur, came to know that we are not going to support "document.layers" in 5.0, so that makes this bug invalid. So I'm going ahead and marking it invalid.
If you are not going to support document.layers it should be undefined instead of null
Severity: normal → enhancement
Status: REOPENED → RESOLVED
Last Resolved: 19 years ago → 19 years ago
Resolution: INVALID → LATER
this will not be addressed for Comm 5.0 commericial product. How about we mark Verified/Later so it gets addressed for 5.1? this is the best way to not lose this enhancement for later.
I'm still interested in understanding why it has to be undefined and not null. Shouldn't the if (document.layers) checks that are out there still fail for a null value? Having said that, I agree that it probably makes sense to do what a non-layers browser would do i.e. return undefined.
*** Bug 11853 has been marked as a duplicate of this bug. ***
Moving all non-DOM, non-crash bugs to M15.
HTML DOM bugs are M11/P2 for Vidur.
In an attempt to get my bug list in order again, marking all the bugs I have currently as ASSIGNED.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago → 18 years ago
Resolution: --- → FIXED
Rather than debate this more, I checked in a change to revert to Nav 4.x behavior - we now return undefined.
Verified with 2000-01-20-09.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.