From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.2 required=3.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id C677F1F47C; Fri, 13 Jan 2023 00:57:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=80x24.org; s=selector1; t=1673571471; bh=HbyI2g+zETqTDLwqHjUqBft6Xq6lRI/y2Orw3W81heE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Zcpg+McJlVlghDoubroqEM6KXN1EkQe6oJcdydidPrUe2INGZdgiMGnbDtXZXcKvg tVzxkrSTomK9U7ncY7AzcYElgE9kg5LBZgVEz5o1HmLOtbXiv5yuaWz2xb1Y4sSTu8 x3RVm3OPgxVuFvG1o8vPSY0v+6cFL36iD3M1R1qk= Date: Fri, 13 Jan 2023 00:57:52 +0000 From: Eric Wong To: Andrei Rybak Cc: meta@public-inbox.org Subject: Re: Accesskeys for keyboard navigation Message-ID: <20230113005752.M69467@dcvr> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: List-Id: Andrei Rybak 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)