Summary: | fast/xpath/namespace-vs-predicate.xhtml fails unexpectedly in no-SVG build | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Mark Rowe (bdash) <mrowe> | ||||||
Component: | DOM | Assignee: | Alexey Proskuryakov <ap> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Major | CC: | ap, cdumez | ||||||
Priority: | P2 | Keywords: | Regression | ||||||
Version: | 523.x (Safari 3) | ||||||||
Hardware: | Mac | ||||||||
OS: | OS X 10.4 | ||||||||
Attachments: |
|
Description
Mark Rowe (bdash)
2007-10-28 05:29:33 PDT
Do you know when this regressed? I'm not quite sure what kind of a bug this is: Firefox seems to have a similar problem with elements in unknown namespaces. Sorry I don't. It's probably been like that for quite a while now. Created attachment 16916 [details]
unknown namespace test case
Firefox and TOT WebKit behave identically on this test (actually, Tiger WebKit does the same). I still don't see why.
Created attachment 18150 [details] fix the test It's actually clear: we do not support xml:id (see bug 16505), and plain "id" is only treated as ID in HTML and SVG content (unless a doctype says that some attribute is an ID, but it doesn't in this case, and we don't even support that, bug 12971). A no-SVG build isn't supposed to know about SVG id attribute. Comment on attachment 18150 [details]
fix the test
r=me
Committed revision 29024. Mass moving XML DOM bugs to the "DOM" Component. |