user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Andrei Rybak <rybak.a.v@gmail.com>
To: meta@public-inbox.org
Subject: Accesskeys for keyboard navigation
Date: Fri, 13 Jan 2023 00:55:40 +0100	[thread overview]
Message-ID: <b5e71493-8b97-e7d6-158c-f5676ccd903b@gmail.com> (raw)

Hello,

First of all, thank you for developing and maintaining public-inbox.

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

So far, five keys are supported:

- z – go from viewing a thread to the list of threads, i.e. "go to
     the front page". Using key "z" for this is borrowed from MediaWiki.
- s – place cursor in the search text field.
- f – go to the "flat" thread view. Useful for going from an individual
     email to the thread.
- n – go to the "nested" thread view.
- t – jump to the "thread overview" at the bottom of threads. You can
     then use tab and shift+tab to select the email to jump to and enter
     to jump to the email in the thread.

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

[1] see https://en.wikipedia.org/wiki/Access_key and
 
https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/accesskey
[2] https://en.wikipedia.org/wiki/Userscript

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.

--
Best regards, Andrei R.

             reply	other threads:[~2023-01-12 23:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 23:55 Andrei Rybak [this message]
2023-01-13  0:57 ` Accesskeys for keyboard navigation Eric Wong
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=b5e71493-8b97-e7d6-158c-f5676ccd903b@gmail.com \
    --to=rybak.a.v@gmail.com \
    --cc=meta@public-inbox.org \
    /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).