As you may know roblox is on quite a few platforms:Windows, Mac, mobile.
But it is also on Chromebook and with that comes a few problems.
I wont go listing all of them, but I’ll just talk about the one that has been bugging me the most
So on Chromebook it uses the google playstore which allows you to download mobile games. One of them being roblox. Now ever since I first used roblox on chromebook i was able to scroll when I was in the app. Then for some reason back in about February of 2020 all of a sudden I’m guessing there was an update which caused you to not be able to scroll on the app. It bugged me a little and I found a few ways to still play games. What I did was I favorited the game on the roblox site. Then open up the roblox and and go to my favorites and play the game. However the only place I can scroll is when I click on my profile. That is the only part of the app I am currently aware is scrollable.
Now that roblox has updated the site and they app with the new recommended page it has basically shifted how to app is. Here is an example of what I am talking about
With this new layout I am unable to easily find and play games that my friends have been playing. Because sometimes I rely on them to find new games.
Here is a video of it in more detail
You should try windowed mode and if windowed then fullscreen, vice versa. If that doesn’t fix it, then you should use the website itself, and when you have to launch a game just click the game, click play(on the website), and there should be a prompt/pop-up which will say something like “Always open these links associated with this app” and make sure it’s check and click open Roblox. If there is no prompt and Roblox doesn’t open, then try updating/reinstalling Chrome. Hope this helps
Oops, should’ve known Chrome OS doesn’t support that… I’ve used Chrome OS like once, but never really sticked with it. Thank you for correcting me, I don’t wanna mislead anyone into actually trying a feature that is currently only available on Windows OS, perhaps Roblox support will fix this at some point in the future…