Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kFjtD-0005CQ-PA for pgsql-www@arkaria.postgresql.org; Tue, 08 Sep 2020 20:06:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kFjtB-000681-AY for pgsql-www@arkaria.postgresql.org; Tue, 08 Sep 2020 20:06:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kFjtA-00067u-Sn for pgsql-www@lists.postgresql.org; Tue, 08 Sep 2020 20:06:48 +0000 Received: from mail-lj1-x241.google.com ([2a00:1450:4864:20::241]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kFjt7-0002e2-Ps for pgsql-www@postgresql.org; Tue, 08 Sep 2020 20:06:47 +0000 Received: by mail-lj1-x241.google.com with SMTP id w3so524347ljo.5 for ; Tue, 08 Sep 2020 13:06:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=03Q2PikRdof+1nbWJKdI88DEFzni5k1NRrHREL1m+3E=; b=fMg9ydl7ZUf+w56r78EUH9La34EfO4vEXE+mVx4zFrgpFJu2gduBWhTpVcUzRyYzs7 Qhrc8nH3eEz8lfuL3LQyVgxnv41f0gYJsSTKmcvP4hLmK31k3b04o7dCUPXhT2OWN2oz zUIcgj80pSpulcJqkizXGKF6RQwgcNuPiQSO8cSFd89Zota3aimYJ7Sraxj4Vr/GWwmj Ru6MFLGFgkxqpNuFgDnr6K43jQj+oL1fm35w3BiGpb637yKo/KyuwTESTNHIC2j9evZh 5gocxqGyt2mJ5Pol1VSwA+mH1QXH6Phxifn2AHa6/IJE2RPJsOUtc0TLJ9hVheWGXdgF VyxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=03Q2PikRdof+1nbWJKdI88DEFzni5k1NRrHREL1m+3E=; b=HA8Ru6nawXFU8jhMhZYEz9MSBKJ8v3QUgTFE3p1NCpqXakCptFZyiBLUjK9yz6vN9i IUY4f9U+JTD+MmRGoH6aZ0Emx4+A/82+JMyilbkBSOALP4nBUHzcmuZb1cvzZBFB+2FT gNKWbTKCyPwo37JzltTCpKmsD9ehNOgT/IJWTSUg15b6cbDEJkalE4X4KcVsseOZd4Tj Uepb9jVMLRV5G+rjpKH9XpMTPv4luy6rj4+3IqBZMLgZXfRwuQalt4QFiBVKynrkpoQG L6p7SH1OC5thFaGhpW0K8BN33QqJognxcTCx/7F0NdTLMDDGfp1RmT+C0rtxqgxpnr8Z 5M3w== X-Gm-Message-State: AOAM532xNKnb1b/O7E47wUq7+QYmdfxvUmPmpdz0XgefkGpDxjBfK5Dv U+8WdcnJ5EsaqLNjA0/EwvfHI0A/ZWsScC6l2WXlSg== X-Google-Smtp-Source: ABdhPJxuNwv6ur/8uyDcuI3yBMOv4czBFlqq/mqy3lVs4mQG7eTPP9K6I1Q8YfXNTVUc96c3gyCLFUIMJYOtu0+x7PQ= X-Received: by 2002:a05:651c:134a:: with SMTP id j10mr86916ljb.337.1599595603487; Tue, 08 Sep 2020 13:06:43 -0700 (PDT) MIME-Version: 1.0 References: <20190102144552.GA1419@momjian.us> <20200908191016.GA3276@momjian.us> <40b59afa-3aaa-a689-979a-b4518e8b4063@postgresql.org> In-Reply-To: <40b59afa-3aaa-a689-979a-b4518e8b4063@postgresql.org> From: Magnus Hagander Date: Tue, 8 Sep 2020 22:06:32 +0200 Message-ID: Subject: Re: Website "Up" link To: "Jonathan S. Katz" Cc: Bruce Momjian , PostgreSQL www Content-Type: multipart/alternative; boundary="000000000000bb00c105aed2df9e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000bb00c105aed2df9e Content-Type: text/plain; charset="UTF-8" On Tue, Sep 8, 2020 at 9:35 PM Jonathan S. Katz wrote: > On 9/8/20 3:10 PM, Bruce Momjian wrote: > > On Wed, Jan 2, 2019 at 09:45:52AM -0500, Bruce Momjian wrote: > >> On Mon, Dec 31, 2018 at 07:37:54PM -0500, Jonathan Katz wrote: > >>> On 12/31/18 6:58 PM, Bruce Momjian wrote: > >>>> I don't see an "Up" link when I am on the first level submenu, e.g.: > >>>> > >>>> https://www.postgresql.org/docs/11/appendixes.html > >>>> > >>>> If I am pressing "Up" from a sub-submenu, it would be good to have an > >>>> "Up" link here too. > >>> > >>> That section of the documentation is loaded in from the source SGML/XML > >>> files - it would have to be added in there. > >>> > >>> If I were to take a guess as to why it is that way, it is because that > >>> "Up" from that section is in actuality the same thing as home "Home." > >>> That said, perhaps the better UX is to keep it consistent, and have > "Up" > >>> available as long as you can navigate up the doc tree. > >> > >> Yes, that was my conclusion as well. We had this issue with the old > >> style sheets too, and I think it was fixed. > > > > FYI, Peter Eisentraut has fixed this. > > Excellent. So that will become available on the pgweb side for supported > releases the next time the docs are loaded, which will be at the next > scheduled update in November. > AFAICT it's only been fixed in the master branch, so unless you're looking at the devel docs you'll be waiting a year longer. And if you're looking at the devel docs, it should already be visible. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --000000000000bb00c105aed2df9e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Sep 8, 2020 at 9:35 PM Jonathan S= . Katz <jkatz@postgresql.org= > wrote:
On 9/8/20 3:10 PM, Bruce Momjian wrote:
> On Wed, Jan=C2=A0 2, 2019 at 09:45:52AM -0500, Bruce Momjian wrote: >> On Mon, Dec 31, 2018 at 07:37:54PM -0500, Jonathan Katz wrote:
>>> On 12/31/18 6:58 PM, Bruce Momjian wrote:
>>>> I don't see an "Up" link when I am on the fi= rst level submenu, e.g.:
>>>>
>>>>=C2=A0 =C2=A0 https://www.postgres= ql.org/docs/11/appendixes.html
>>>>
>>>> If I am pressing "Up" from a sub-submenu, it wou= ld be good to have an
>>>> "Up" link here too.
>>>
>>> That section of the documentation is loaded in from the source= SGML/XML
>>> files - it would have to be added in there.
>>>
>>> If I were to take a guess as to why it is that way, it is beca= use that
>>> "Up" from that section is in actuality the same thin= g as home "Home."
>>> That said, perhaps the better UX is to keep it consistent, and= have "Up"
>>> available as long as you can navigate up the doc tree.
>>
>> Yes, that was my conclusion as well.=C2=A0 We had this issue with = the old
>> style sheets too, and I think it was fixed.
>
> FYI, Peter Eisentraut has fixed this.

Excellent. So that will become available on the pgweb side for supported releases the next time the docs are loaded, which will be at the next
scheduled update in November.

AFAICT it= 's only been fixed in the master branch, so unless you're looking a= t the devel docs you'll be waiting a year longer. And if you're loo= king at the devel docs, it should already be visible.=C2=A0

--
=C2=A0Magnus Hagander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: https://www.redpill-l= inpro.com/
--000000000000bb00c105aed2df9e--