[wwwdocs] gcc-6/changes.html: diagnostics, Levenshtein, -Wmisleading-indentation, jit (v2)

On Tue, 19 Jan 2016, Jakub Jelinek wrote:
> Perhaps we need to use something other than <b style='color:magenta'>...</b>
> and similar, the question is what.  It certainly worked well back almost 3
> years ago when I've added those into gcc-4.9/changes.html.

And interestingly it still does when I download the page and view
it locally (Firefox 43 or Google Chrome).

Instead of hardcoding <b style='color:red'>text</b> it makes sense
to use <span class="boldred">text</span> which is easier (and easier
to tweak, and I just applied the patch below.

Interestingly enough, same result:  Looks just fine when viewed
locally; https://gcc.gnu.org/gcc-6/changes.html in the browser
does not show the color, though it validates. :-(

Hmm.

Gerald

On Tue, Jan 19, 2016 at 11:49:27PM +0100, Gerald Pfeifer wrote:
> On Tue, 19 Jan 2016, Jakub Jelinek wrote:
> > Perhaps we need to use something other than <b style='color:magenta'>...</b>
> > and similar, the question is what.  It certainly worked well back almost 3
> > years ago when I've added those into gcc-4.9/changes.html.
> 
> And interestingly it still does when I download the page and view
> it locally (Firefox 43 or Google Chrome).
> 
> Instead of hardcoding <b style='color:red'>text</b> it makes sense
> to use <span class="boldred">text</span> which is easier (and easier
> to tweak, and I just applied the patch below.

Note, we want to tweak gcc-{4.9,5}/changes.html too, and there are more
colors than just red in there.
Also, seems the colors disappeared also from e.g.
https://gcc.gnu.org/projects/cxx1z.html
which has
  <style type="text/css">
      /* <![CDATA[*/
        tr.separator { background: #ffffcc}
        .supported { color: green }
        .unsupported { color: red }
      /* ]]> */
    </style>

	Jakub

On Tue, 19 Jan 2016, Jakub Jelinek wrote:
> Note, we want to tweak gcc-{4.9,5}/changes.html too, and 
> there are more colors than just red in there.

Yes, I just got tired and need to log off now.

> Also, seems the colors disappeared also from e.g.
> https://gcc.gnu.org/projects/cxx1z.html

Lovely.

It seems gcc.gnu.org enforces a strict Content Security Policy
(cf. http://www.html5rocks.com/en/tutorials/security/content-security-policy/
for example) which does not allow for inline CSS styles.

  Content-Security-Policy: default-src 'self' http: https:

So either we get the configuration of the web server changed, or
indeed we need to touch all those existing pages.

Gerald

On Wed, Jan 20, 2016 at 12:17:36AM +0100, Gerald Pfeifer wrote:
> On Tue, 19 Jan 2016, Jakub Jelinek wrote:
> > Note, we want to tweak gcc-{4.9,5}/changes.html too, and 
> > there are more colors than just red in there.
> 
> Yes, I just got tired and need to log off now.
> 
> > Also, seems the colors disappeared also from e.g.
> > https://gcc.gnu.org/projects/cxx1z.html
> 
> Lovely.
> 
> It seems gcc.gnu.org enforces a strict Content Security Policy
> (cf. http://www.html5rocks.com/en/tutorials/security/content-security-policy/
> for example) which does not allow for inline CSS styles.
> 
>   Content-Security-Policy: default-src 'self' http: https:
> 
> So either we get the configuration of the web server changed, or
> indeed we need to touch all those existing pages.

At least the warning/error/note styles are something that multiple pages are
using and going to use in the future, so if that could be defined in the
main gcc.css, it would be enough.

	Jakub

On Wed, Jan 20, 2016 at 12:40:08AM +0100, Jakub Jelinek wrote:
> On Wed, Jan 20, 2016 at 12:17:36AM +0100, Gerald Pfeifer wrote:
> > On Tue, 19 Jan 2016, Jakub Jelinek wrote:
> > > Note, we want to tweak gcc-{4.9,5}/changes.html too, and 
> > > there are more colors than just red in there.
> > 
> > Yes, I just got tired and need to log off now.
> > 
> > > Also, seems the colors disappeared also from e.g.
> > > https://gcc.gnu.org/projects/cxx1z.html
> > 
> > Lovely.
> > 
> > It seems gcc.gnu.org enforces a strict Content Security Policy
> > (cf. http://www.html5rocks.com/en/tutorials/security/content-security-policy/
> > for example) which does not allow for inline CSS styles.
> > 
> >   Content-Security-Policy: default-src 'self' http: https:

BTW, is that also the reason why very recently the gcc.gnu.org homepage
changed layout (the News column is much wider than the Release Series and Status
column), at least with Firefox 43.0?  The page has:
<td style="width: 50%; padding-right: 8px;" valign="top">
etc.

	Jakub

On Wed, 20 Jan 2016, Jakub Jelinek wrote:
>>> It seems gcc.gnu.org enforces a strict Content Security Policy
>>> (cf. http://www.html5rocks.com/en/tutorials/security/content-security-policy/
>>> for example) which does not allow for inline CSS styles.
>>> 
>>>   Content-Security-Policy: default-src 'self' http: https:
> BTW, is that also the reason why very recently the gcc.gnu.org homepage
> changed layout (the News column is much wider than the Release Series and Status
> column), at least with Firefox 43.0?  The page has:
> <td style="width: 50%; padding-right: 8px;" valign="top">

Yes, exactly!

I had addressed most of that back then last year, and now finally
completed the last missing pieces.

(There are only two bits of local "style=" left on our web site, 
in projects/gupc.html.)

Gerald