Position not working on Chromebook Linux/Crostini

[hkclark]

Thanks for the great extension! My guess is that this is something about the Chromebook Crostini and there might not be anything that can be done about it, but I thought I would check just in case. I'm using Firefox v129.0.2 on the latest version of Crostini on ChromeOS v127.0.6553.132. The resize in resizeit2 is working great (including setting it at startup), but the window never moves, regardless of what settings I put in for Left & Top (and I am sure that the position checkbox is checked). With Google's plans in the near future to killing things like uBlock Origin, I want to get Firefox working well on my Chromebook (plus, I just like Firefox so much better). Unfortunately the initial windows for Firefox seem to show up tiny... especially if you open up a private window, but even the main window starts tiny (without resizeit2) in the middle of the screen and adjusts somewhat is size... but now most of it is off the screen. :-( Resizeit2 is great for getting me back to the correct size, but it's still very annoying to have the top-left corner of the screen approximately at the center of the screen and most of it is off the right and bottom. Let me know if I can do anything on this end to help. Thanks!

[hkclark]

Unfortunately I'm going to be away from my normal computers fora bit, but something like this could be handy (esp in a VM) for people who don't have a Chromebook and want to try to recreate it:

https://techpp.com/2021/07/12/install-chrome-os-on-laptop-pc-guide/

I'll try it as soon as I have decent access to a "normal PC" (at this point I'm assuming the issue will show up in ChromeOS regardless if it's on a Chromebook or not, but I don't know for sure until I test it. Thanks!

[fuzzykiller]

Hey, thank you for reporting this. Unfortunately it would appear that all resources on installing Chrome OS on a regular PC (or in a VM) are gone. Google has acquired Neverware and is no longer offering CloudReady. As such, I cannot work on this. Someone with a ChromeOS device would have to.

My guess that this is down to how Chrome OS does window management. It is unlikely there’s anything I could do to fix this. Instead, Firefox itself would have to address this.