Closed
Bug 32833
Opened 25 years ago
Closed 8 years ago
Implement ID/IDREF(S) linking
Categories
(Core :: XML, enhancement, P3)
Core
XML
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: hjtoi-bugzilla, Assigned: hjtoi-bugzilla)
References
Details
ID/IDREF(S) is the basic form of XML linking:
<?xml version="1.0"?>
<!DOCTYPE memo [
<!ATTLIST ref
xref IDREF #REQUIRED
>
<!ATTLIST para
unique ID #IMPLIED
>
]>
<memo>
<title>Title here</title>
<para>Here is a <ref xref="id1">link</ref> .</para>
<para unique="id1">This is the link target.</para>
</memo>
A linking element is recognized by noticing that it has a non-empty attribute
whose type is either IDREF or IDREFS (IDREFS is the plural, several link targets
can be specified in one attribute, separated by spaces). Currently there is no
support for this in the parser nor in the DOM.
A target can be an element with a unique id (a non-empty attribute whose type is
ID). Currently there is no support for this in the parser (see bug 10292), but
DOM 2 at least should have the GetElementById method in the DOMDocument
interface (this is not yet implemented).
ID/IDREF(S) linking enables linking inside a document, it cannot be used to link
to other documents.
Assignee | ||
Comment 1•25 years ago
|
||
I now have CVS account, assigning XML linking related bugs to me
(heikki@citec.fi).
Assignee: nisheeth → heikki
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•25 years ago
|
||
How should we inform the user about IDREFS links that have multiple targets?
I think I have the solution for the case when the link has been clicked: provide
a popup menu listing all the targets. The user must select the target s/he
wishes to travel to.
The problem is with mouse over. What to show in the status bar? Normally we show
the full URI, but if there are several IDREFS targets we quickly run out of
space... Should we show a tooltip with all the targets? If so, there is still
the problem with status bar.
I added Ian Hickson to CC because he has had good and related comments in bug
1995.
Comment 3•25 years ago
|
||
Well, the full URI is always in this document, isn't it? So there won't be much
to show in the status bar anyway.
http://www.foobar.net/somewhere/page.xml#one, #two, #three, #four
...or just:
#one, #two, #three, #four
...in fact.
Comment 4•25 years ago
|
||
Setting target milestone to Future so that this does not show up on PDT's
radar...
Target Milestone: --- → Future
Assignee | ||
Comment 5•25 years ago
|
||
With the new Expat we should have the ID part covered, but that still leaves
IDREF(S). James Clark said in an email that his new Expat does not/will not(?)
include support for IDREF(S) attribute(s). We would need to add that ourselves I
guess.
Updated•25 years ago
|
QA Contact: chrisd → petersen
Assignee | ||
Updated•25 years ago
|
Target Milestone: Future → mozilla1.2
Assignee | ||
Updated•24 years ago
|
Target Milestone: mozilla1.2 → Future
Updated•23 years ago
|
QA Contact: petersen → rakeshmishra
Updated•22 years ago
|
QA Contact: rakeshmishra → ashishbhatt
Updated•21 years ago
|
Severity: normal → enhancement
Summary: FEATURE: Implement ID/IDREF(S) linking → Implement ID/IDREF(S) linking
Updated•16 years ago
|
QA Contact: ashshbhatt → xml
Comment 6•8 years ago
|
||
Per https://dom.spec.whatwg.org/ we should only support an id attribute.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•