Chrome browser support broken for Tech Forums and Wiki pages

**First problem… Chrome browser support for these Tech Forums.
**
The following is a screenshot. You can see that the block of text that should be placed below the banner image is floating in the top left corner. I say “floating” because if you scroll the page a bit or mouse in the general area the text changes or partially vanishes.

https://en.opensuse.org/images/d/d5/Tech_Forums_Chrome_rendering_problem.png
Second problem - Chrome CSS and possibly scripting broken thoroughly for Wiki pages.

When I use a Chrome browser to browse my Wiki page (or likely any other Wiki page), the text is displayed unformatted as though the CSS is just not read. Also, any scripting like logging in is non-functional, without inspecting the code I’ll speculate that pop-up logon window may be implemented in the CSS as well.

Both these problems were first noticed beginning this past Friday (3 days ago), so I suspect that some website update was applied on or about then.

These problems do not appear when using either a Firefox or Edge browsers.

TSU
BTW - Yeah, some of you might notice that I am looking at OpenShift, too…

Tony, I’ve seen this too. To check whether this was a Chrome-version specific issue, I downgraded Chrome, issue gone. Then accidently updated Chrome again and I haven’t seen the issue reappear. Which left me puzzled. I suscpect a badly parsed file in the cache, but like said, I cannot reproduce the issue.
Did you already try to remove Chrome’s cache?

Same issue on Vivaldi here - clearing caches seems to have at least temporarily fixed the issue ( |Vivaldi|1.13.1008.34 (Stable channel) (64-bit)|
|—|—|

Verified on Chrome Version 62.0.3202.94 (Official Build) (64-bit)

Clearing browser cache fixed the problem.


Kim - 12/12/2017 8:17:34 AM

Hey kgroneman:

>Verified on Chrome Version 62.0.3202.94 (Official Build) (64-bit)
>
>Clearing browser cache fixed the problem.

Installed Chrome Version 63.0.3239.84 (Official Build) (64-bit) and didn’t see
the issue.


Kim - 12/12/2017 8:33:18 AM

Cleared <only> the cache (didn’t touch all the other data that can be cleared) and then reloaded the page.
Initially on reload, the problem was still there but when I scrolled the page but when the page was scrolled, that cleared the problem.

Looks like clearing the cache seem to have solved the Wiki page CSS problem, too (or something else changed since 10 hours ago).

Here’s hoping the cache is the problem and solution.

TSU