CSS problem

[bablukid]

Hi
The issue numbers cant be displayed since many roundups.

looks like you're loading the fonts with "http" whiel the page is in "https", so the browser doesnt want to load the font resource.

Message from Chrome on Win10 =
Mixed Content: The page at 'https://haxe.io/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Open+Sans:600,400,700,800|Gentium+Book+Basic:400,700,400italic,700italic'. This request has been blocked; the content must be served over HTTPS.

[skial]

Thanks for this, I thought I had pushed the changes to server, but apparently not 😅

[skial]

@bablukid The cache for the index has been cleared, so hopefully now it's all https for you.

[bablukid]

nope, sorry :)

<link rel="stylesheet" type="text/css" href="/css/normalize.css" />
<link rel="stylesheet" type="text/css" href="/css/normalize-opentype.css" />
<link rel="stylesheet" type="text/css" href="/css/haxe.io.css" />
<link rel="stylesheet" type="text/css" href="//fonts.googleapis.com/css?family=Open+Sans:600,400,700,800|Gentium+Book+Basic:400,700,400italic,700italic" />
<link rel="stylesheet" type="text/css" href="/css/frontpage.css" />

[skial]

I just fired up a windows 10 vm with chrome 48 on sauce labs and its doesn't appear to be reporting any mixed content warnings anymore. If you view the recording, goo into fullscreen so you can read the text, the video is pretty weak quality.

Did you try a hard refresh?

[bablukid]

even after a cache delete, a restart of chrome, or a Ctrl+F5 I still get the problem.
With firefox no prob.
Now the fonts are correctly loaded, so now the problem is purely from CSS.
the titles style ( html[class="/"] main li h1 ) uses Arial, and strangely if I remove this style it displays well.
It works also if I keep arial and remove only "font-weight: normal;"

...strange.... anyway if I'm the only one to get this, give it up

[skial]

No your not the only one, a similar issue came up before, #201. But I couldn't figure out the problem.

Thanks for testing it out on your end, I appreciate it. I now have something a little more concrete to look into.