Bug 12971 - An ID attribute declared in a DTD internal subset is not treated as such
Summary: An ID attribute declared in a DTD internal subset is not treated as such
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 523.x (Safari 3)
Hardware: Macintosh OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
: 18605 (view as bug list)
Depends on:
Blocks: 18605
  Show dependency treegraph
 
Reported: 2007-03-05 11:42 PST by Alexey Proskuryakov
Modified: 2019-02-06 09:04 PST (History)
7 users (show)

See Also:


Attachments
test case (1021 bytes, text/html)
2007-03-05 11:43 PST, Alexey Proskuryakov
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Proskuryakov 2007-03-05 11:42:27 PST
In a plain XML document with the following DTD, CODE should work as an ID attribute, but it doesn't.

<!DOCTYPE ROOT [
  <!ELEMENT CHILD2 (#PCDATA|GCHILD)*>
  <!ATTLIST CHILD2 attr1 CDATA #IMPLIED
                   CODE ID #REQUIRED>
]>
Comment 1 Alexey Proskuryakov 2007-03-05 11:43:01 PST
Created attachment 13480 [details]
test case
Comment 2 Sam Weinig 2007-03-05 15:12:24 PST
I am not sure if we have a bug for dbaron's tests, but this issue is also illustrated in http://dbaron.org/css/test/xmlid from his test suite.
Comment 3 Alexey Proskuryakov 2010-09-22 13:36:36 PDT
*** Bug 18605 has been marked as a duplicate of this bug. ***
Comment 4 William J. Edney 2010-10-28 15:28:08 PDT
I can also confirm this.

Major pain when trying to use getElementById() with arbitrary XML.

Cheers,

- Bill
Comment 5 Lucas Forschler 2019-02-06 09:04:13 PST
Mass moving XML DOM bugs to the "DOM" Component.