user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Andrei Rybak <rybak.a.v@gmail.com>
Cc: meta@public-inbox.org
Subject: Re: Accesskeys for keyboard navigation
Date: Fri, 13 Jan 2023 00:57:52 +0000	[thread overview]
Message-ID: <20230113005752.M69467@dcvr> (raw)
In-Reply-To: <b5e71493-8b97-e7d6-158c-f5676ccd903b@gmail.com>

Andrei Rybak <rybak.a.v@gmail.com> wrote:
> Hello,
> 
> First of all, thank you for developing and maintaining public-inbox.

You're welcome :>

> I'm a frequent user of accesskeys [1] so I've written a user script [2]
> to add them to some links on websites running public-inbox. The user
> script is available via Greasy Fork, a website for hosting user scripts:
> 
>     https://greasyfork.org/en/scripts/458141-accesskeys-for-public-inbox

Cool.  I've long intended for the HTML output to be stable
enough something like that.

Please feel welcome post here if there's new developments or
discussion to be had about it.

Fwiw, there's also rel=prev / rel=next for paginated pages;
but I forgot how browsers use them :x

> Any feedback, especially ideas for other uses of accesskey on
> public-inbox websites would be appreciated.

Do you know if there's commonly-used accesskeys for normal git repo
viewers?  (cgit/gitweb/etc...)

The /$INBOX/$OID/s/ endpoint (linked from @@ diff hunk headers)
is being extended to support "normal" git repositories meant for
code (WIP: https://80x24.org/lore/pub/scm/git/git.git/ ) and
I'd like to avoid conflicts.

> P.S. I've looked at source code of public-inbox to try adding support for
> accesskeys natively, but my Perl knowledge is very limited, so I
> decided against trying to implement it on my own for a patch.

No worries.  I will consider it if I find time (some other things
take priority atm).

Do you happen to know what happens if a page defines accesskeys
which conflict with userscripts?  I prefer avoiding breakage for
existing userscript users if implemented in public-inbox itself.

I am a bit hesitant to recommend browser extensions in the
documentation/help output itself since Stylish was found to be
spyware in the past.  (that goes for downloading and running
anything from the Internet w/o auditing it, first, public-inbox
included)

  reply	other threads:[~2023-01-13  0:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 23:55 Accesskeys for keyboard navigation Andrei Rybak
2023-01-13  0:57 ` Eric Wong [this message]
2023-01-15 11:43   ` Andrei Rybak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230113005752.M69467@dcvr \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    --cc=rybak.a.v@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).