From: Luis Felipe via Guix-patches via <guix-patches@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Mathieu Othacehe <othacehe@gnu.org>,
"47663@debbugs.gnu.org" <47663@debbugs.gnu.org>
Subject: [bug#47663] [PATCH] website: Add Help dropdown menu
Date: Fri, 09 Apr 2021 19:51:50 +0000 [thread overview]
Message-ID: <eDO1rx9LekchmcIgattkzA_lRu040BLm8aaCIrzv0x3cVwa2cAHTPcmYSQw6_S_5O5qI7nM5QPDT2_RD35qIyeZCvuQ2MMzNk-EO06Iovxg=@protonmail.com> (raw)
In-Reply-To: <20210409191243.xgvp6c5jdammt6h3@pelzflorian.localdomain>
On Friday, April 9, 2021 7:12 PM, pelzflorian (Florian Pelz) <pelzflorian@pelzflorian.de> wrote:
> Thank you for working on this.
>
> On Fri, Apr 09, 2021 at 08:55:50PM +0200, Mathieu Othacehe wrote:
>
> > At first I thought that left clicking the
> > "Help" menu would open it. Adding a dedicated item in the list also
> > seems fine.
>
> In commit 571e1a416e1148139923418bf801ddb6b11723c3 I made left-click
> toggle the dropdown instead because touch devices cannot otherwise
> access the dropdown, I think. Am I mistaken?
I think that is the right behavior, Florian. So I'll add the missing link as a new item, like so:
Help
+ All ← Links to /help/
+ Etc.
+ Etc.
And fix any remaining style issues for pointing and touch devices (cursor shouldn't be pointer (it wasn't before), and dropdown menu width should not shrink on click).
next prev parent reply other threads:[~2021-04-09 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 19:49 [bug#47663] [PATCH] website: Add Help dropdown menu Luis Felipe via Guix-patches via
2021-04-09 6:51 ` Mathieu Othacehe
2021-04-09 13:32 ` Luis Felipe via Guix-patches via
2021-04-09 18:55 ` Mathieu Othacehe
2021-04-09 19:12 ` pelzflorian (Florian Pelz)
2021-04-09 19:51 ` Luis Felipe via Guix-patches via [this message]
2021-04-10 15:24 ` Luis Felipe via Guix-patches via
2021-04-10 18:51 ` Mathieu Othacehe
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='eDO1rx9LekchmcIgattkzA_lRu040BLm8aaCIrzv0x3cVwa2cAHTPcmYSQw6_S_5O5qI7nM5QPDT2_RD35qIyeZCvuQ2MMzNk-EO06Iovxg=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=47663@debbugs.gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=othacehe@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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://git.savannah.gnu.org/cgit/guix.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).