Re: Doc images are broken

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, PostgreSQL www <pgsql-www(at)postgresql(dot)org>
Subject: Re: Doc images are broken
Date: 2023-02-21 21:05:48
Message-ID: CABUevEyisAEaxusm77nuYTW-JrgAYVghkSRm+Q1C=m-becc+nw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Tue, Feb 21, 2023 at 8:34 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:

> On Tue, Feb 21, 2023 at 11:21 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> > Perhaps the word "distorted" was overstating it. The black border
> > definitely isn't supposed to be there, though.
>
> Chrome Developer mode shows me the following error when run against
> the page in question (which is
> https://www.postgresql.org/docs/13/storage-page-layout.html)
>
> "Refused to apply inline style because it violates the following
> Content Security Policy directive: "style-src 'self'
> fonts.googleapis.com tagmanager.google.com". Either the
> 'unsafe-inline' keyword, a hash
> ('sha256-TSlN9iIwid/izE/G6oaDB90xp+keZMu2WTr1Y7Gnrrc='), or a nonce
> ('nonce-...') is required to enable inline execution. Note that hashes
> do not apply to event handlers, style attributes and javascript:
> navigations unless the 'unsafe-hashes' keyword is present."
>
> I'm no expert, but this definitely seems relevant to me.
>

That does seem to be it. I've applied a patch that allows "unsafe-inline"
styling on the SVGs in docs and it looks much better now.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Peter Geoghegan 2023-02-21 21:10:55 Re: Doc images are broken
Previous Message Peter Geoghegan 2023-02-21 19:34:25 Re: Doc images are broken