Re: bad style for SECURITY DEFINER - Mailing list pgsql-www

From Jonathan S. Katz
Subject Re: bad style for SECURITY DEFINER
Date
Msg-id 3686660c-02a4-7b06-98e9-34a30bb7be08@postgresql.org
Whole thread Raw
Responses Re: bad style for SECURITY DEFINER  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-www
On 12/13/21 9:01 AM, Justin Pryzby wrote:
> 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

The below seems to do the trick. Tested in Chrome, FF, and Safari. 
Screenshot attached.

If no objections I'll push the patch tomorrow.

Thanks,

Jonathan

diff --git a/media/css/main.css b/media/css/main.css
index d97da4d..955f612 100644
--- a/media/css/main.css
+++ b/media/css/main.css
@@ -877,6 +877,10 @@ code,
    font-size: inherit !important;
  }

+#docContent h2 code {
+  margin: 0.5em;
+}
+
  #docContent .NAVHEADER table th,
  #docContent .navheader table th {
    text-align: center;


Attachment

pgsql-www by date:

Previous
From: Stephen Andert
Date:
Subject: Requesting editor access
Next
From: Daniel Gustafsson
Date:
Subject: Re: bad style for SECURITY DEFINER