all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Arsen Arsenović" <arsen@aarsen.me>
To: Gavin Smith <gavinsmith0123@gmail.com>
Cc: Yuri Khan <yuri.v.khan@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: Online HTML manuals for Emacs missing important CSS
Date: Mon, 03 Apr 2023 11:10:19 +0200	[thread overview]
Message-ID: <86jzyttjn3.fsf@aarsen.me> (raw)
In-Reply-To: <ZCnV/rG6xBsWq9Kn@starmint>

[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]


Gavin Smith <gavinsmith0123@gmail.com> writes:

> On Mon, Apr 03, 2023 at 01:01:47AM +0700, Yuri Khan wrote:
>> On Sun, 2 Apr 2023 at 20:11, Gavin Smith <gavinsmith0123@gmail.com> wrote:
>> 
>> > There are ś (pilcrow) symbols visible indicating copiable links.
>> >
>> > texi2any outputs CSS rules to hide these unless the users moves their
>> > mouse pointer over the text:
>> >
>> > a.copiable-link {visibility: hidden; text-decoration: none; line-height: 0em}
>> > span:hover a.copiable-link {visibility: visible}
>> 
>> How do these rules behave on mobile browsers where there is no mouse?
>
> I've just tested it with Brave 1.49.132 on Android 8.1.0 and it appears
> that the links appear when you tap on the text they are next to.
> They disappear when you tap elsewhere on the page.

This is browser specific.  You can use the following as a workaround:

  @media (hover: none) {
      /* Presume the user will have difficulty hovering.  Make clickable
         anchors visible.
       */
      a.copiable-link {
          visibility: visible;
      }
  }
-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]

      reply	other threads:[~2023-04-03  9:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-02 13:10 Online HTML manuals for Emacs missing important CSS Gavin Smith
2023-04-02 18:01 ` Yuri Khan
2023-04-02 19:22   ` Gavin Smith
2023-04-03  9:10     ` Arsen Arsenović [this message]

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

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

  git send-email \
    --in-reply-to=86jzyttjn3.fsf@aarsen.me \
    --to=arsen@aarsen.me \
    --cc=gavinsmith0123@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=yuri.v.khan@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.