Closed
Bug 374507
Opened 17 years ago
Closed 17 years ago
getElementById doesn't find <area> elements
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
VERIFIED
INVALID
People
(Reporter: jwatt, Unassigned)
Details
Attachments
(2 files)
getElementById doesn't find <area> elements
Comment 1•17 years ago
|
||
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.
Comment 2•17 years ago
|
||
<area> is found in xhtml because parser/content sink doesn't remove it. That is at least what I guess.
Reporter | ||
Comment 3•17 years ago
|
||
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
Comment 4•17 years ago
|
||
Note that per HTLM5 it's a bug to drop <area> currently.
Comment 5•14 years ago
|
||
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.
Description
•