Stewart Gordon <> changed:

           What    |Removed                     |Added
          Component|DMD                         |websites
           Severity|minor                       |enhancement

--- Comment #9 from Stewart Gordon <> 2012-03-11 17:13:51 PDT ---
(In reply to comment #7)
> It _is_ a dmd issue. dmd generates the ddoc documentation. The javascript 
> stuff
> which runs after that doesn't even _have_ the information necessary to produce
> the proper hierarchy. The anchor generation prevents it, because it generates
> anchors which have been stripped of their hierarchy.

You're wrong, it _does_ have all the information it needs, in the form of the
anchor's position in the DOM.  Indeed, I've managed to fix it by adding one
line to the JS code:

    for (var i = 0; i < document.anchors.length; i++)
        var a = document.anchors[i];
        var text =;
        if (a.parentNode.parentNode.parentNode.tagName == "DD") continue;
        if (hash[text] > 0) continue;
        hash[text] = 1;
        values[n++] =

While it would be nice to have a hierarchical list of links, it's distinct from
the reporter's request, and so warrants a separate RFE.  From a DMD point of
view, it's a matter of the Ddoc macro system providing access to the full
hierarchical name of the symbol.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to