This only happens with Discourse after you “add to homepage” (creating a Progressive Web App), once added, they don’t respect Auto-Rotate settings and keep rotating even when the setting is disabled on Android.
It’s incredibly frustrating since I always have “auto-rotate” turned off and it’s constantly switching between landscape and portrait view, especially when laying down on the couch or in bed on Discourse communities (Asana, Airtable, this community, etc.).
Sounds like a problem with Android. The obvious solution is to just use your browser that works instead of the one that doesn’t. It’s unclear whether this can be solved on the Discourse side.
That’s what I thought at first, but it is only happening with Discourse PWA’s, not happening with any other PWA’s we have set up and are using which brought me back to guessing it’s an issue with Discourse.
I rely incredibly heavily on the PWA’s for Discourse, jumping into each community from the home screen so simply just “using chrome directly” isn’t easy and a painful “workaround”.
I wouldn’t have posted in this community if I wasn’t fairly sure that it’s a Discourse issue moreso than an Android issue.
Here’s a video showing off the issue. As you can see, the only PWA that I open which respects screen-lock is the non-Discourse forum. You can see specifically when I visit the non-Discourse PWA for the 2nd time, the bottom-right corner shows the Android Pie screen-lock override control, whereas all of the Discourse forums just automatically rotate and it’s incredibly jarring
When you say that you had this enabled, what exactly did you have enabled? I’d assume that auto-rotate would be controlled by Android at a system-level across the board, why should a specific site be able to override it? If you take a look at the video I attached, you can see how jarring it is to the end-user. Discourse specifically is ignoring the auto-rotate setting.
And with Android Pie, they make it so easy to switch to landscape mode to temporarily override your auto-rotate setting by prompting you in the bottom-right corner:
So those who want to switch to landscape when they have auto-rotate turned off get the best of both worlds when just letting the system control this functionality.
Er empfiehlt, die OS-Option zu nutzen, um die Drehung zu stoppen. Der hier vorliegende Bericht (den ich nachvollziehen kann) besagt jedoch, dass die OS-Option nicht beachtet wird. Das sieht für mich nach einem Contribute > Bug aus.
@codinghorror, ich glaube, du erinnerst dich rückwärts.
Du hast es genau richtig erfasst Falcos Antwort zu lesen, ist genau so, wie ich erwartet hätte, dass es funktioniert, und ich kann nachvollziehen, warum sich Leute beschweren – das ist nämlich genau das, was mich in letzter Zeit wahnsinnig macht. Egal, ob ich die automatische Drehung an oder aus stelle, Discourse verhält sich immer so, als wäre die automatische Drehung “eingeschaltet”. Es ignoriert völlig die Android-Schnelleinstellungs-Option, die als Vorschlag gegeben wurde, um das ständige Drehen zu stoppen. Das muss ein Bug sein.
Whoops, sorry for finding the wrong post @Falco. Looks like you did remember correctly @codinghorror, apologies!
In my mind the correct value is whatever one respects the OS setting. If I have rotation lock on, the app shouldn’t be rotating. If I have auto-rotate on, the app should rotate like the OS does. Given that Android 9 supports locking the device in landscape, this will (hopefully) make everyone happy.
Side note, the Discourse Hub app functions as I just described above - it respects the OS.
