Thread: Issue with dev doc builds, fonts
I noticed that a local website style build of the Postgres docs looked odd. Chrome's console revealed that there was some issue with downloading fonts. Attached are errors from Chrome's console. There is a 404 error for the URL https://www.postgresql.org/media/css/bootstrap.min.css.map, plus something about a CORS policy. Thanks -- Peter Geoghegan
Attachment
On Sat, Apr 2, 2022 at 1:14 AM Peter Geoghegan <pg@bowt.ie> wrote:
I noticed that a local website style build of the Postgres docs looked
odd. Chrome's console revealed that there was some issue with
downloading fonts.
Attached are errors from Chrome's console. There is a 404 error for
the URL https://www.postgresql.org/media/css/bootstrap.min.css.map,
plus something about a CORS policy.
The .map file is normal and nothing to care about. That's basically it trying to download "debugger symbols" as a separate file and we don't provide those (eh. not the same thing, but the closest C analogy I could find).
The CORS policy might be more annoying. How are you actually viewing the files -- through a localhost web server, or just by opening the files?
On Sat, Apr 2, 2022 at 8:17 AM Magnus Hagander <magnus@hagander.net> wrote: > The CORS policy might be more annoying. How are you actually viewing the files -- through a localhost web server, or justby opening the files? Just opening the files. The font looks off. -- Peter Geoghegan
On Sat, Apr 2, 2022 at 5:23 PM Peter Geoghegan <pg@bowt.ie> wrote:
On Sat, Apr 2, 2022 at 8:17 AM Magnus Hagander <magnus@hagander.net> wrote:
> The CORS policy might be more annoying. How are you actually viewing the files -- through a localhost web server, or just by opening the files?
Just opening the files. The font looks off.
For local files, I think it can never work.
Now, for something like a localhost webserver it could, but we're ont setting CORS headers on the fonts. I've updated our webservers to send that header now -- it might be worth trying again with just the local file as well.
On Sat, Apr 2, 2022 at 9:40 AM Magnus Hagander <magnus@hagander.net> wrote: > Now, for something like a localhost webserver it could, but we're ont setting CORS headers on the fonts. I've updated ourwebservers to send that header now -- it might be worth trying again with just the local file as well. That seems to have fixed the problem. Thanks! -- Peter Geoghegan