* Accesskeys for keyboard navigation
@ 2023-01-12 23:55 Andrei Rybak
2023-01-13 0:57 ` Eric Wong
0 siblings, 1 reply; 3+ messages in thread
From: Andrei Rybak @ 2023-01-12 23:55 UTC (permalink / raw)
To: meta
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.
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Accesskeys for keyboard navigation
2023-01-12 23:55 Accesskeys for keyboard navigation Andrei Rybak
@ 2023-01-13 0:57 ` Eric Wong
2023-01-15 11:43 ` Andrei Rybak
0 siblings, 1 reply; 3+ messages in thread
From: Eric Wong @ 2023-01-13 0:57 UTC (permalink / raw)
To: Andrei Rybak; +Cc: meta
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)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Accesskeys for keyboard navigation
2023-01-13 0:57 ` Eric Wong
@ 2023-01-15 11:43 ` Andrei Rybak
0 siblings, 0 replies; 3+ messages in thread
From: Andrei Rybak @ 2023-01-15 11:43 UTC (permalink / raw)
To: Eric Wong; +Cc: meta
On 13/01/2023 01:57, Eric Wong wrote:
> Andrei Rybak <rybak.a.v@gmail.com> wrote:
>> 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
As far as I know, rel attribute has more to do with search engine
optimization.
However, having these attributes does make finding the links with
document.querySelector much easier for my script. I've added navigation
for next/prev pages to the script.
>
>> 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...)
None that I know of, and I would guess that it isn't present in any of
them, really. Confluence (wiki from Atlassian) has them, but Bitbucket
(Git hosting from Atlassian) does not. (Side note: both of them also
implement their own custom shortcuts).
> 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.
Conflicts won't be a problem, because there wouldn't be a lot of users
of the user script. I'll just adjust my script, if needed.
>> 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.
When there is a conflict, Firefox, as an example, just shows the user
every link with the same accesskey, as if the user was navigating over
them using TAB key.
> 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)
Yeah, the Stylish debacle wasn't pleasant.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-01-15 11:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-12 23:55 Accesskeys for keyboard navigation Andrei Rybak
2023-01-13 0:57 ` Eric Wong
2023-01-15 11:43 ` Andrei Rybak
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).