After some digging I have learned, Stadia relies on the return value of the likes of `window.screen.width`, ignoring that the value is untrue as it gets decreased on high-density screens. For exampl...
See more...
After some digging I have learned, Stadia relies on the return value of the likes of `window.screen.width`, ignoring that the value is untrue as it gets decreased on high-density screens. For example, my screen is 3840px wide, `screen.width` reports it as 2254px. You could be tempted to take into account the devicePixelRatio—which once more will get you, Stadia dev, an erroneous result (press F12): ```js // DO NOT DO this, unless you like tinkering with floating point numbers. width = window.screen.width * (window.devicePixelRatio || 1); width // is 3454, which still isn’t the correct 3840 ``` … better yet, query something that doesn’t get changed on zoom levels or system text scaling settings. (Please forward it to the devs, @ChrisFromGoogle , as I believe this could help and save time.)