Closed Bug 374507 Opened 17 years ago Closed 17 years ago

getElementById doesn't find <area> elements

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: jwatt, Unassigned)

Details

Attachments

(2 files)

Attached file testcase
getElementById doesn't find <area> elements
Looks more like "area elements that are broken and unusable by not being inside
a map element aren't added to the DOM" to me.
Attached file xhtml testcase
<area> is found in xhtml because parser/content sink doesn't remove it.
That is at least what I guess.
Phil: That fixes it. Thanks. I guess for backwards compatibility things should stay as they are.

Smaug: yeah, I know the XML parser doesn't throw away elements like the HTML parser, but HTML is what's widely used out there so that's what I'd prefer my tests to use.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Note that per HTLM5 it's a bug to drop <area> currently.
Component: DOM: Core → DOM: Core & HTML
QA Contact: ian → general
Note that the original test case now works, thanks to the new HTML parser.
Assignee: general → nobody
Status: RESOLVED → VERIFIED
OS: Windows XP → All
Hardware: x86 → All
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: