[Webkit-unassigned] [Bug 16505] getElementById fails to find xml:id identified elements (xml:id support)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Dec 25 23:45:56 PST 2007


http://bugs.webkit.org/show_bug.cgi?id=16505





------- Comment #2 from eric at webkit.org  2007-12-25 23:45 PDT -------
Test cases I can think of that we would need:

1.  Test null:id vs. xml:id, which wins when both are defined?
2.  Test multiple xml:id's (the parser will throw an error, i'm pretty sure)
3.  Test xml:id in HTML (we should probably ignore it)
4.  Text xml:id attribute normalization
  a. get the value via js (getAttribute, getAttributeNS, other ways?), which
are normalized?
  b. set the value via js, see that it's properly normalized
  c. use getElementById to find normalized names.  should getElementById
normalize its args?
5.  Possibly test lookup across documents.  an HTML document embedding an XML
document, calling objectElement.contentDocument.getElementById() how is
normalization handled, etc.

I think that's all we need to start with.  Writing those test cases will
probably take longer than adding the support into Element.cpp, and adding the
attribute name into xmlnames.in. :)

It's possible that Hixie or others have already made some of the tests we might
need.  Heck, the W3c might even have a test suite for xml:id (I kinda doubt
it).


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list