From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
Cc: | "Karl O(dot) Pinc" <kop(at)karlpinc(dot)com>, pgsql-www(at)postgresql(dot)org |
Subject: | Re: The release notes page could use a "javascript required" warning |
Date: | 2024-11-11 14:54:22 |
Message-ID: | CA+OCxowyMNethvNKbd2hcAa8+E0pPXsZ5O4PX7zZbEH+eQKS4Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Mon, 11 Nov 2024 at 14:47, Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
> On 11/8/24 1:16 PM, Karl O. Pinc wrote:
> > Hi,
> >
> > The page of release notes,
> > /docs/release/,
> > could use a "javascript is required" warning.
> > (Or the page could be re-engineered to omit
> > the drop-downs and just display the point releases
> > when js is off.)
> >
> > Clicking on a PG version link without javascript turned
> > on does nothing.
>
> Arguably we can remove the JavaScript and make it just a really long
> page that has everything listed out (similar to the way it was in the
> docs).
>
> Outside of the cleaner look, I'm can't remember why we set up the
> interface in this way (and I'm pretty sure the person who did it is
> typing this email). I'm not necessarily opposed to just listing
> everything out, though the page does get rather long if you're looking
> for a really old release announcement (which is likely not too many
> people).
>
It shouldn't be overly hard to statically render everything initially, and
then have the JS collapse everything.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL:
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2024-11-11 14:55:57 | Re: The release notes page could use a "javascript required" warning |
Previous Message | Jonathan S. Katz | 2024-11-11 14:47:24 | Re: The release notes page could use a "javascript required" warning |