public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug web/107650] Sphinx generated web pages don't have "up" (to the section TOC) Date: Sun, 13 Nov 2022 19:48:51 +0000 [thread overview] Message-ID: <bug-107650-4-VauV5ZsgXC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107650-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107650 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Martin Liška from comment #3) > (In reply to Andrew Pinski from comment #0) > > The texinfo generated HTML has an up link which links to the section that > > the page is linked from. > > While the Sphinx generated HTML does not. > > An example for texinfo is > > https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/eBPF-Options.html#eBPF-Options > > compared to > > https://gcc.gnu.org/onlinedocs/gcc/gcc-command-options/machine-dependent- > > options/ebpf-options.html . > > > > Is there a way to get this feature back? as it is useful when browsing the > > manual. > > No, I don't think it was useful as one was missing complete navigation that > is right now on the left. Except the navigation does not fully replace the up button. An example is if you scroll down on the top level TOC down to the "Nios II Options" (not on the navigation on the left) and click it. The navigation on the left does not scroll down to the same location. Making it harder to figure out where you are. > > > > > The other thing that would be a nice feature back is having next/previous/up > > links at the start also and not just at the end of the page. > > > > The order of previous and next on the bottom of the page is ok even though > > it is swapped from what it was previously. > > The layout is better in Sphinx as it corresponds to expect layout (similarly > to web browsers). So that is broken. Having it on the top and the bottom is still useful. Maybe you clicked the wrong link but it was the next one you either have to use the left/right links at the buttom or you have to understand the left/right curser keys are bound to previous/next page. Again still confusing. Most web UI designers have ignored UI design for years how humans work and just make broken things we should not repeat the same mistakes.
next prev parent reply other threads:[~2022-11-13 19:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-11 20:51 [Bug web/107650] New: Sphinx generated web pages don't have up (to the section index) pinskia at gcc dot gnu.org 2022-11-11 20:54 ` [Bug web/107650] " pinskia at gcc dot gnu.org 2022-11-13 17:43 ` [Bug web/107650] Sphinx generated web pages don't have "up" (to the section TOC) pinskia at gcc dot gnu.org 2022-11-13 19:33 ` marxin at gcc dot gnu.org 2022-11-13 19:48 ` pinskia at gcc dot gnu.org [this message] 2022-11-14 8:43 ` marxin at gcc dot gnu.org
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=bug-107650-4-VauV5ZsgXC@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).