From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: David Gow <davidgow@google.com>,
Sadiya Kazi <sadiyakazi@google.com>,
linux-doc@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH RFC V2] docs: Add more information to the HTML sidebar
Date: Sat, 4 Feb 2023 09:20:13 +0900 [thread overview]
Message-ID: <0749ec79-4375-e44e-f2b6-8f0a8bfa9ad9@gmail.com> (raw)
In-Reply-To: <877cwys3g6.fsf@meer.lwn.net>
On Fri, 03 Feb 2023 17:02:17 -0700, Jonathan Corbet wrote:
> Jonathan Corbet <corbet@lwn.net> writes:
>
>> As before, the results can be seen at:
>>
>> https://static.lwn.net/kerneldoc/
>
> What's there now reflects a couple of tweaks beyond the patch I sent.
>
> Hopefully I've addressed some of the concerns... One thing I really
> don't like about the auto-positioning sidebar, though, is that it pushes
> the "The Linux Kernel" heading off-screen. For somebody following a
> link into the docs from elsewhere, that could be a bit confusing.
That's the same in RTD. So this might be a point you hate RTD, I guess.
But I see a major problem on small/narrow screens.
The sidebar is now kept at the top, and by clicking/tapping a link in the
TOC, I can't jump to the section I want to see.
Sorry, but this is not usable at all.
> I
> know vaguely how to fix it with CSS, but getting such things right
> always require a fair amount of dinking around and I can't do that now.
;-) ;-) ;-)
Thanks, Akira
>
> jon
next prev parent reply other threads:[~2023-02-04 0:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 23:09 [PATCH RFC V2] docs: Add more information to the HTML sidebar Jonathan Corbet
2023-02-04 0:02 ` Jonathan Corbet
2023-02-04 0:20 ` Akira Yokosawa [this message]
2023-02-04 7:33 ` Akira Yokosawa
2023-02-04 21:39 ` Jonathan Corbet
2023-02-04 0:02 ` Randy Dunlap
2023-02-06 19:25 ` Jonathan Corbet
2023-02-14 18:25 ` Randy Dunlap
2023-02-14 18:33 ` Jonathan Corbet
2023-02-15 10:23 ` Akira Yokosawa
2023-02-16 23:55 ` Jonathan Corbet
2023-02-04 4:36 ` David Gow
2023-02-06 11:22 ` Sadiya Kazi
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=0749ec79-4375-e44e-f2b6-8f0a8bfa9ad9@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=sadiyakazi@google.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox