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 depends on the web browser: > > > > https://www.w3schools.com/TAGs/att_accesskey.asp > > > > I don't know whether this is possible (this may require Javascript), > > but access keys should be related to the current position. > > > > The following seems to work for the non-XS code:
I applied a similar patch. > 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, so it may happen for other split options than node. Should we set USE_ACCESSKEY on automatically only if split at node? -- Pat
