[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: link handling in js-reader
From: |
Gavin Smith |
Subject: |
Re: link handling in js-reader |
Date: |
Thu, 4 Mar 2021 20:16:49 +0000 |
User-agent: |
Mutt/1.9.4 (2018-02-28) |
On Wed, Mar 03, 2021 at 08:25:59PM -0600, Jacob Bachmeyer wrote:
> Per Bothner wrote:
> > [...]
> > Ideally, one could determine which links are internal by checking for an
> > entry in the table-of-contents. However, that is bit complicated,
> > mainly because sub-pages don't have access to the ToC, so it would
> > have to involve message sending between JavaScript contexts (no big
> > deal).
> > [...]
> > Comments?
>
> The texinfo tool that generates HTML has the ToC, so really the correct
> solution here would be for the HTML output to include the 'target'
> attributes directly. JS can then determine internal links by the absence of
> that attribute and the features at least somewhat gracefully degrade if JS
> is disabled.
I don't know why you say that the manual does not degrade gracefully if
JS is disabled.
> This leads to another question: are the Info manuals to be taken as a
> collective whole? Phrased differently, should a link to a node in a
> different Info manual be considered "external"?
Yes as this JavaScript system only handles one manual. It doesn't handle
links to other Texinfo manuals differently to any other external link.