Open
Bug 110817
Opened 22 years ago
Updated 1 year ago
Nested XLinks don't work consistently
Categories
(Core :: XML, defect)
Tracking
()
NEW
Future
People
(Reporter: rubydoo123, Unassigned)
References
()
Details
(Keywords: testcase)
Attachments
(5 files, 1 obsolete file)
The above mentioned nested xlink test displays an error in mozilla processing. If you hover over the links, the displayed target in the status bar all point to the a.xml document. If you left-click on each link, the resulting target for all links is a.xml. If you context menu select each target, they all go to the correct locations : a=a.xml, b=b.xml, c=c.xml I will attach all of the related files with this test case, just in case it gets removed from the site.
Reporter | ||
Comment 1•22 years ago
|
||
This is the xml test case, the three css files that I am attaching are associated with this file. If you copy everything to your system, you will need to adjust the paths for the css files.
Reporter | ||
Comment 2•22 years ago
|
||
This is one of three css files mentioned in the test file : abc.css
Reporter | ||
Comment 3•22 years ago
|
||
This is the second fo three css files mentioned in the test file
Reporter | ||
Comment 4•22 years ago
|
||
This is the third and final css file mentioned in the test file
The left-click (and hover but that is only because XML Base has not been used) behaviour is the correct one. XLinks don't nest; the outermost link is the only link there is.
Reporter | ||
Comment 6•22 years ago
|
||
I contacted the HTML WG W3C rep, and this was his response to the not able to nest xlinks comment: That is NOT true. Unfortunately this is not obvious from the XLink REC, but resolution of XLink issue #25 [1] says: Resolution: Allow nested links, add non-normative examples to make sure implementors don't miss the point. though, it seems editors forgot to add appropriate examples :-( A good example is SVG, SVG's `a' element uses simple XLink [2] and it can be nested. Existing SVG implementations, such as Adobe's SVG Viewer, do behave correctly with those nested links. [1] http://www.w3.org/XML/2000/12/LinkingIssueList.html#XL25 [2] http://www.w3.org/TR/SVG/linking.html#Links Regards, -- Masayasu W3C - World Wide Web Consortium
*goes back to check the REC* You are right, I misread the REC. The REC states: "If a simple-type element contains nested XLink elements, such contained elements have no XLink-specified relationship to the parent link." I read that carelessly to read no nested links. Sorry about the confusion. Changing summary to "Nested XLinks don't work consistently".
Summary: Links navigate to incorrect location using xlink → Nested XLinks don't work consistently
Updated•22 years ago
|
Target Milestone: --- → Future
Updated•21 years ago
|
QA Contact: petersen → ian
Attachment #58417 -
Attachment is obsolete: true
Also reproduced using FF 0.9.1 on Win XP; setting OS=All.
Keywords: testcase
OS: Windows 98 → All
Comment 10•19 years ago
|
||
The behavior of nexted XLinks should eventually be similar to nested xhtml:a links. I do not think we want to special-case either.
Updated•18 years ago
|
Assignee: hjtoi-bugzilla → xml
QA Contact: ian → ashshbhatt
![]() |
||
Comment 11•18 years ago
|
||
Should eventually be fixed by bug 211916.
![]() |
||
Comment 12•18 years ago
|
||
Actually this seems to have been fixed on trunk by something else. I don't know by what, or when it happened. It's completely fixed in SeaMonkey trunk, and the only reason it's not fixed in Firefox trunk is because of a hack that bug 325652 exists to back out. The backout may actually take place in bug 331959. I don't have time to investigate myself, but if someone else does, I'd be very interested to know what fixed this.
![]() |
||
Comment 13•18 years ago
|
||
*** Bug 297558 has been marked as a duplicate of this bug. ***
Updated•14 years ago
|
Assignee: xml → nobody
QA Contact: ashshbhatt → xml
Updated•1 year ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•