DOM can't see <OL> type when it is set to decimal

VERIFIED FIXED in M12

Status

()

Core
DOM
P2
normal
VERIFIED FIXED
18 years ago
17 years ago

People

(Reporter: Jan Carpenter, Assigned: vidur (gone))

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

18 years ago
Overview Description:
When <OL type=1> is set (see attachment), DOM doesn't read anything.
(works fine when set to "I" or "A" etc, just not for "1")

Actual Results:
when document.write is used to display the contents of <OL type=1>, nothing is
displayed

Expected Results:
should display a 1

Build Date & Platform Bug Found:
1999091410 Win98  (Because of different bug, you must use Viewer)

Additional Builds and Platforms Tested On:
Mac, Linux, WinNT
(Reporter)

Comment 1

18 years ago
Created attachment 1685 [details]
attaching testcase

Updated

18 years ago
Priority: P3 → P2
Target Milestone: M11

Comment 2

18 years ago
Triage: setting to M11/P2.
HTML DOM bugs are M11/P2 for Vidur.

Updated

18 years ago
QA Contact: gerardok → janc

Comment 4

18 years ago
The original testcase uses:

  var oList=document.firstChild.childNodes[1].childNodes[1];

which might cause problems since the BODY element is actually:

  document.firstChild.childNodes[2]

in more recent builds because the whitespace between HEAD and BODY is
document.firstChild.childNodes[1] (see bug 17026).

Attaching revised testcase that uses getElementById to ensure we get the OL
nodes. When tested with Linux (RH6.0) build 1999102608, the type of the first
list (<ol id="first" type="1">) is null as indicated in the original bug report.

Comment 5

18 years ago
Created attachment 2436 [details]
revised testcase
Moving to M12 as this is relatively higher priority (DOM1 tree representation
completeness).
Target Milestone: M11 → M12
Moving to M12 as this is relatively higher priority (DOM1 tree representation
completeness).
(Assignee)

Updated

18 years ago
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
(Assignee)

Comment 8

18 years ago
Fixed on 11/11/1999. Good find!
(Reporter)

Updated

18 years ago
Status: RESOLVED → VERIFIED
(Reporter)

Comment 9

18 years ago
Thanks

Verified.
You need to log in before you can comment on or make changes to this bug.