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
yes, the pop up for launching the game. They've now turned it into basic UI template elements.
Anyway, what exactly broke?
You mean the Themes system? used to it could apply the theme completely on the Client UI, ever since they changed it Themes don't apply correctly, for instance the background of the steam pages wont apply the theme, along with many of the UI elements don't display theme fonts correctly etc.
Themes have been broken for a while. hell some themes can no longer display the fonts correctly and they end up overlapping off the elements their trying to display on.
Now as for that V4 stuff. This CSS-based nonsense (I'm not of the highest of opinion of using CEF as a cross-platform UI toolkit, it's not like there weren't any alternatives either, especially ones more lenient on system resources but that's besides the point of this thread) CAN BE MODIFIED! People have been doing that already!
If you want to stop Steam from updating, you have to stop it from updating manually.
Use a file explorer and go to: C:\Steam\
Create a new text file in that folder called: 'steam.cfg'
Type and save this text in this file:
BootStrapperInhibitAll=enable
BootStrapperForceSelfUpdate=disable
I believe then you will receive no more updates. And whenever you want to receive updates again, you can remove that text from the file.
Accurately describes 80% of the steam app, visuals or not. Someone with lacking knowledge at some point decided to use CEF and now they're stuck with it.
The whole CEF/webhelper baseline is causing a lot of bugs and issues too, because it's an overcomplicated thing for the job and basically emulates a whole little internet + server + browser + reskin just to display a gui. The very idea of the concept is laughable if you think of it from a basic software engineering perspective.
Must be a nightmare to secure, too.
Google doesn't even try to secure Chromium or CEF memory wise. Google believes in garbage sandboxing per container and is now trying to dump memory locking into things like the Linux kernel. if memory serves me well, the Linux call was mlock, which locks the memory address for the application. I also don't recall the Chromium dev not being a dumbass and leaving an unlock function in the kernel pull they submitted, in essence once the memory is locked it cannot be unlocked....