From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Org FAQ design (Re: [PATCH] org-faq.org: Inline comments)
Date: Sun, 2 Jul 2023 12:46:06 +0700 [thread overview]
Message-ID: <u7r2v0$cm9$1@ciao.gmane.io> (raw)
In-Reply-To: <8735271wpo.fsf@localhost>
On 01/07/2023 22:24, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>>> FAQ is probably fine. We may add a CSS there that will fold the
>>> answers by default.
>>
>> When all entries are opened, it is possible to use search in browser. I
>> am against the idea of hiding answers. However the table of contents,
>> that is rather long and revealed on hover only, makes it harder to
>> search in the TOC at first.
>
> I am now watching
> https://fosdem.org/2023/schedule/event/a11y_eaa_bfsg_wcag_wai_aria_wtf/
I have skimmed through the presentation.
> They suggest a combination of <details><summary> to keep hidden text
> searchable. See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/summary
Unsupported by Firefox:
https://bugzilla.mozilla.org/show_bug.cgi?id=1724299
Implement auto-expanding <details>
I am unsure if it is possible to implement auto-expanding on link to
specific question for Firefox.
However <details> is better than accordions in most cases.
I would consider to put TOC into <details open>
P.S. Have you noticed that MDN pages have "skip to content" link hidden
by default, but revealed on using keyboard (TAB).
next prev parent reply other threads:[~2023-07-02 5:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 0:04 Inline comments ypuntot
2023-06-22 1:50 ` Max Nikulin
2023-06-28 15:51 ` [PATCH] org-faq.org: " Max Nikulin
2023-06-29 10:47 ` Ihor Radchenko
2023-06-30 10:34 ` Max Nikulin
2023-07-01 10:48 ` Ihor Radchenko
2023-08-06 18:34 ` Bastien Guerry
2023-07-01 15:24 ` Ihor Radchenko
2023-07-02 5:46 ` Max Nikulin [this message]
2023-07-08 5:48 ` [PATCH v2] " Max Nikulin
2023-07-08 9:31 ` Ihor Radchenko
2023-07-10 16:09 ` Max Nikulin
2023-09-01 11:28 ` Ihor Radchenko
2024-04-15 12:17 ` Ihor Radchenko
2024-04-17 14:44 ` Max Nikulin
2024-04-20 11:14 ` Trailing whitespace after export snippets without a transcoder (was: [PATCH v2] org-faq.org: Inline comments) Ihor Radchenko
2024-04-20 15:02 ` Trailing whitespace after export snippets without a transcoder Max Nikulin
2024-04-21 13:00 ` Ihor Radchenko
2024-04-22 10:45 ` Max Nikulin
2024-04-22 19:01 ` Ihor Radchenko
2024-04-25 10:54 ` Max Nikulin
2024-04-28 11:19 ` Ihor Radchenko
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='u7r2v0$cm9$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.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://git.savannah.gnu.org/cgit/emacs/org-mode.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).