Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
before anything else,i just wanted to find out if i was the only one experience the issue or it's something affecting others as well
Error Reference: Store_9004704_83d69629d753cc1d
Loading chunk 4970 failed.
(missing: https://store.akamai.steamstatic.com/public/javascript/applications/store/chunk~0f0129d36.js?contenthash=f391f1e910f19d14ad43)
for example
Loading chunk 2805 failed.
Same issue though. Some asset is not being called for some reason resulting in a black box that hides whatever is behind it.
What browser does steam rely on? Chromium? I wonder if they started using settings of the default browser. Mi firefox is locked down as tight as my snare drum. No java allowed. No third party cookies. No ads. No nothing is allowed on my browser. Rightfully so. I hate ads and they spy on you anyway so you do not get to do that and if your site breaks because of that and i cant see it then i ht the back button. I do not start giving you permissions.
truly a nightmare
for the record,those pages open just fine if i use my regular browser (firefox)
It’s pretty annoying.
They must have changed something in javascript and using a feature not included in old browsers. This is just speculation, maybe I'm wrong.
however,i cannot get them to display anything on mobile (steam app) and on the steam client
which is pretty damn annoying
By the way, the error also happens on my old chrome v91. So it's not because we're not using chrome.
Something javascript related is my guess. Maybe a browser version check before it shows up the chunk.