Thema: [bug]pressroom mixed up

it is like that for some time on PC in firefox, brave is ok....cleared cache....

Lapporta has a similar situation, for him only transfer and office tab are workin properly:

We are both using Firefox

If you are the only person reporting such problem, most probably the problem is at your side.
For me pressroom works fine in Firefox, Chrome, Brave.

Tnx that was really helpful.

Ps if you read 2nd post then you can see that other user Lapporta(my bad, forgot to write that Lapporta is another user) also has a similar problem.

And in third post i wrote that we are both using Firefox.

PSS latest Firefox version, tried to clear cache

imho, the problem is on your side, or maybe it's Firefox problem, maybe some ads blocking is enabled and blocks too much (although, I dont know why it should be a problem but just in case you can try disabling it)

it also might be slow connection problem

as other workarounds I would suggest trying private browsing mode in Firefox

and as a last resort opening all this links below and refreshing the page w/o cache on them (ctrl+shift+r):
https://sokker.org/_next/static/css/4284b7bc9f2a2b47.css
https://sokker.org/_next/static/css/31289946596ca5e9.css
https://sokker.org/_next/static/css/c7b5661b2881180a.css
https://sokker.org/_next/static/css/ec74218194129ac5.css
https://sokker.org/_next/static/css/f1a1dc4b1d6073e8.css

imho I think also that it is on my side, but where should I post that problem?

tried turning off addblock but it did not help, private browsing did.


this last resort helped. ty. what did this things do? instaled some virus? :)
i could google ctrl+shift+r but this other .css? what do you think that the problem was?

i will get back to you if it helped also in other case....

from image you posted it looks like some css files (page stylesheet files - defining where, what element should bee on the page, what size and properties should it have etc.) are not loaded during loading sokker, so I gave You direct links to all those files hoping that after they will be opened, the browser will handle the problem it has now