I don't see the problem locally.

Could you open developer tools to see if any error is logged
on console or network tab?

Thank you for the feedback, I did what you asked me and today it happened again. You can find the errors in the attachment.

Please let me know what I can do to fix this.

Deleted: Capture.PNG 206 KB

	Capture.PNG 206 KB View Download

Thank you for providing more feedback. Adding requester "kochi@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thanks for taking the screenshot.

From what I see in the screenshot, the page seems trying to load CSS resources
from some unexpected URL, 'http://deunp7845fran2p.grouphc.net:8080/auth?du=...',
where 'https://assets-cdn.github.com' is expected.

I guess this is that you are in a controlled network (e.g. corporate network
or hotel/public wifi) that it redirects any page to some login authentication page,
and for some reason you had the cache for the top-level HTML file.
I think Chrome is working fine, just your network situation is causing the issue.

Probably you will get better support on user forum for this issue.
https://productforums.google.com/forum/#!forum/chrome

Please feel free to come back and reopen, if this is not your network or
environment issue but a Chrome's bug.

Thank you again for the feedback. IMHO I do not think it is a network bug. My reasons for thinking this are:
- Internet Explorer never fails. If it was a network issue, the problem should also occur there.
- I can see the page, just not the layout. If it was a network issue, all would be blocked or nothing.

Might it have something to do with proxy stuff that Chrome can't handle correctly?

Also you might check your extensions.
Anyway, this will be better supported at the user forum.

This doesn't reproduce on our environment, so unless you can explain
what factor is causing Chrome to load GitHub's static CSS files via
...grouphc.net:8080... URL, not from assets-cdn.github.com, we cannot
determine what is a bug in Chrome, and we can never make progress.

Internet Explorer may just work, and Chrome might have some corner case
bug, but anyhow it is not reproducible for us, at least we have to identify
what are different (network, proxy, etc.) from you and us.

Do you have any idea about the domain "grouphc.net"?
I think this is quite unlikely Chrome has that hard-coded, or GitHub provided
that URL in their pages.

Grouphc.net is the company domain where my client is in now. I know they use proxy here, but I don't know how I can find the differences between your environment and mine. Is there maybe a tool somewhere in Chrome that we can run, so we can compare the output of the reports?

Then the course of action would be to ask the IT management people
within grouphc.net?
Google or Chrome has nothing to do with them.

I've already done this and they told me it works in IE so it should work in Chrome. But if we can't compare both mine and your system, we can't find the difference. I guess you guys test Chrome to work with proxy's too?

In general Chrome supports web proxy, but we cannot investigate how a specific
proxy in grouphc.net works.  If you are already contacting with them, why not
ask them directly try Chrome and demonstrate the failure?

You're absolutely right, but they are a bit stubborn and probably feel like this isn't a priority for them as they only support IE.

Anyhow, I appreciate the help. In case of GitHub I'll just use IE then, no worries.

Alright, thanks for the report and sorry not resolving the issue itself.
As is often the case with corp IT network, and understandable.

If you yourself can investigate further why that fails with Chrome only,
it would be helpful for us.
(e.g. try directly loading the CSS file in Chrome, gather network log, identify
where it goes wrong)

Thank you for the friendly help Kochi. I don't have the skills to do what you suggest, so I was hoping there would be a bug reporting tool within Chrome. I used it plenty of times but nothing happened. That's why I opened the bug report here and hoped there would be another log/trace type of tool in Chrome to detect where it goes wrong. Maybe this can be a suggestion for a future release? It would be really helpful to send a report to you guys with all the details, so you can have a better understanding and view on the problem.

No worries, for now, we have a workaround. Have a nice day.

The NextAction date has arrived: 2018-02-07

Going a bit further on thie the IT guys requested me to define the proxy explicitly and set the port on the client. This solved the issue.

I cannot imagine this to be a solid solution for the future. Should something like this not be handled correctly by Chrome or the Proxy server?

Setting the following:
- Internet Options > Connections > LAN settings: Proxy server: Use a proxy for your LAN with Address and Port filled in.

Works 100% of the time to get Chrome to retrieve the CSS from GitHub properly, in case it wasn't before. The strange thing is, when I un-check the tick box and go to GitHub again, even on other tabs and other GitHub pages, it works fine too.

Is there a reasonable explanation why it always works after modifying the direct proxy to on/off?

Again,

Probably you will get better support on user forum for this issue.
https://productforums.google.com/forum/#!forum/chrome

That's where I started:
https://productforums.google.com/forum/#!topic/chrome/LrAj1P2TldU;context-place=topicsearchin/chrome/github