This is a collection of link objects, each one corresponding to an anchor or area tag in the document. This array may be identical to the anchors array if there are no <AREA> tags present.
Note that in Netscape , the class type for these link objects is actually Url and so they are described in detail at that point in the lexically sorted topics.
Objects are added to this array if they are hyperlinks. Simple named anchors do not qualify for addition to this array although they would be added to the array accessible via the document.anchors property. The anchors, and links arrays allow you to distinguish easily between internal and external HREF values. It is slightly confusing in that all <A> tags will be members of the anchors array while only externally linking <A> tags and all <AREA> tags will be in the links array.
DOM level 1 requires that this collection should include all objects instantiated by <AREA> and <A> HTML tags which contain an HREF="..." HTML tag attribute.
Be aware that if you are not using some NAME or ID binding to the <A> and <AREA> tags, you may get unexpected results if new links are added and you are accessing elements of this array using numeric index values.
There are security limitations to what you can do when accessing the links property of a document in another frame. So long as both documents came from the same server, you can access one from the other. Documents from the same domain can access one another as can signed documents according to the security policy in force at run-time.
It isn't proven conclusively but Netscape 6.0 may have some incipient bugs that prevent write-access to properties of objects in this collection. That may be corrected quite quickly as the browser is more widely released.