On 11/10/22 10:35, Gerald Pfeifer wrote:
On Thu, 10 Nov 2022, Martin Liška wrote:
What do you think of keeping the latest under this shorter and simpler
URL (too), though?
Works for me.
:
I believe a symlink (in the file system) on gcc.gnu.org could pull that
off.
Yep, please do so.
Done.
https://gcc.gnu.org/install/ is back with a new face.
But it's not working properly due to some Content Security Policy:
Refused to apply inline style because it violates the following Content Security Policy
directive: "default-src 'self' http: https:". Either the 'unsafe-inline'
keyword, a hash ('sha256-wAI2VKPX8IUBbq55XacEljWEKQc4Xc1nmwVsAjAplNU='), or a nonce
('nonce-...') is required to enable inline execution. Note also that 'style-src' was not
explicitly set, so 'default-src' is used as a fallback.
gcc.gnu.org/:42 Refused to execute inline script because it violates the following
Content Security Policy directive: "default-src 'self' http: https:". Either
the 'unsafe-inline' keyword, a hash
('sha256-ySvT2PEZeueHGC1y2crNuNTfphBynFPP7i+U21fEgX0='), or a nonce ('nonce-...') is
required to enable inline execution. Note also that 'script-src' was not explicitly set,
so 'default-src' is used as a fallback.
gcc.gnu.org/:47 Refused to apply inline style because it violates the following Content
Security Policy directive: "default-src 'self' http: https:". Either the
'unsafe-inline' keyword, a hash ('sha256-biLFinpqYMtWHmXfkA1BPeCY0/fNt46SAZ+BBk5YUog='),
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. Note also that 'style-src' was not explicitly set, so
'default-src' is used as a fallback.
gcc.gnu.org/:202 Refused to load the image 'data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg"; viewBox="0 0 24 24" stroke-width="1.5" stroke="currentColor" fill="none"
stroke-linecap="round" stroke-linejoin="round"><path d="M0 0h24v24H0z" stroke="none"/><circle cx="10" cy="10" r="7"/><path d="m21
21-6-6"/></svg>' because it violates the following Content Security Policy directive: "default-src 'self' http: https:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.
Can you please take a look at it?
Will you be reverting the link adjustments back from /onlinedocs/install/
to plain /install/ ?
Yes, I can do that.
Note how in style.mthml we have some special provisions for install/.
Over the last years I have reduced those to a large extent. There is still
a little bit post-processing going on right now including setting our CSS
and our favicon.
Well, the entire content of gcc.gnu.org/onlinedocs/install/ is *one* of
our documentations and there should not be anything special about it.
Does it make sense?
Yes, things have evolved historically and there was a time we
needed/wanted to treat /install especially, for example to retain
the same (white) background color across.
By now, if we are to make changes, we probably should rather make them
across all of /onlinedocs - favicon and our CSS being two such changes.
Not a critical priority, though, I guess.
Gerald
