On Wed, May 21, 2025 at 09:36:38AM +0200, Patrice Dumas wrote:
> > Thanks for the report. I suppose we should avoid outputting the accesskey
> > attribute for non-split output.
>
> Actually, the issue happens for other split options that end up with
> more than one node/section in an HTML page, s
On Mon, May 19, 2025 at 09:35:31PM +0100, Gavin Smith wrote:
> On Tue, May 13, 2025 at 04:28:28PM +0200, Vincent Lefevre wrote:
> > "texi2any --html --no-split" generates many accesskey attributes
> > with the same value. This does not make sense. In particular, the
> > behavior in such a case depe
> > The following seems to work for the non-XS code:
> >
> > diff --git a/tta/perl/Texinfo/Convert/HTML.pm
> > b/tta/perl/Texinfo/Convert/HTML.pm
> > index c68559c7eb..3435405254 100644
> > --- a/tta/perl/Texinfo/Convert/HTML.pm
> > +++ b/tta/perl/Texinfo/Convert/HTML.pm
> > @@ -9247,6 +9247,13 @
On Mon, May 19, 2025 at 09:35:31PM +0100, Gavin Smith wrote:
> On Tue, May 13, 2025 at 04:28:28PM +0200, Vincent Lefevre wrote:
> > "texi2any --html --no-split" generates many accesskey attributes
> > with the same value. This does not make sense. In particular, the
> > behavior in such a case depe
On Tue, May 13, 2025 at 04:28:28PM +0200, Vincent Lefevre wrote:
> "texi2any --html --no-split" generates many accesskey attributes
> with the same value. This does not make sense. In particular, the
> behavior in such a case depends on the web browser:
>
> https://www.w3schools.com/TAGs/att_acc
"texi2any --html --no-split" generates many accesskey attributes
with the same value. This does not make sense. In particular, the
behavior in such a case depends on the web browser:
https://www.w3schools.com/TAGs/att_accesskey.asp
I don't know whether this is possible (this may require Javascr
