Date: Mon, 13 Dec 2021 08:01:10 -0600
From: Justin Pryzby <pryzby@telsasoft.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
	pgsql-www@postgresql.org
Subject: Re: bad style for SECURITY DEFINER
Message-ID: <20211213140110.GU17618@telsasoft.com>
References: <20211213001707.GR17618@telsasoft.com>
 <236bee0a-b624-b35d-516a-da7e4c3d2358@enterprisedb.com>
 <212DF319-94A5-4827-9F78-74D29C888717@yesql.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <212DF319-94A5-4827-9F78-74D29C888717@yesql.se>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: 
 <https://www.postgresql.org/message-id/20211213140110.GU17618%40telsasoft.com>
Precedence: bulk

On Mon, Dec 13, 2021 at 02:11:24PM +0100, Daniel Gustafsson wrote:
> > On 13 Dec 2021, at 11:35, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
> > 
> > On 13.12.21 01:17, Justin Pryzby wrote:
> >> The title of this section looks poor in the first two web browsers I tried.
> >> https://www.postgresql.org/docs/current/sql-createfunction.html#id-1.9.3.67.10.2
> >> | Writing SECURITY DEFINER Functions Safely
> > 
> > This appears to be a web site styling issue.  It looks more reasonable when I use the default style.
> 
> Agreed, the <code> class should not override the font size of the <h2> and
> should have a different margin than when rendered elsewhere.  It's not entirely
> clear to me why we set a font-size at all, I can't see which case that's
> supposed to be fixing but my CSS is really rusty so I'm sure to be missing
> something.  However, this should be moved to -www where it can be dealt with.

So done.