luceos The mobile experience is not as good as 1.4.1, e.g. the fixed width scrolling is not working

      cilia can you provide a screenshot and/or video of whats happening? Also it would be very helpful to see your php flarum info to find out if there is an incompatibility with an extension).

          cilia what browser and device is this?

          I cannot reproduce this on Android.

          PS. I like to point out that older versions are not supported anymore. And with the recently published vulnerability I urge you to remain on the latest v1.6.2. Issues like these are usually not hard to fix, especially if the behavior hasn't existed in the past. But rolling back to an older version will only guarantee you will never upgrade, and as such will risk getting hacked in the future.

              luceos Thanks for the advice! Yes you're right, this behavior never happened during 1.4.1

                  cilia are you able to provide some versions to these as well? That could help us narrow it down. Does this behavior only happen on Flarum sites by the way? Not that it is an iOS feature..

                      @cilia I think that's a normal behavior on iPhone for all websites, it's not a bug. It's like that since I remember it and the idea is that sliding right/left would navigate forward/back through the browsing history, however when there are no pages to go back or forwards, it does that slight scrolling then centers back itself. I find it an intuitive way to let you know that the navigation back/forward is not possible. And BTW, I use the navigate back gesture a lot when browsing Flarum forums.

                      P.S. Actually there is a problem. When scrolling a Flarum discussion both vertical and horizontal scroll bars appear and that’s wrong. Apparently the page width is slightly bigger than the screen width and the browser allows to scroll the discussion 1-2 pixels to the left (as if there is some space to the right beyond the right screen border). Something has been broken indeed. This is observed when a discussion is opened and not on the main page. Is it possible that the CSS is broken?

                        CyberGene cilia I can confirm that this is happening on the current Safari version on iOS. I have no old 1.4.1 installation for reference but it’s definitely happening on discussion pages. Not on the discussion overview though.

                            luceos The iOS version is 16.1.1, and I can confirm this only happens to flarum discussion page but not the 'all discussions' page. And I clearly remembered it happened after I upgraded to 1.5.0. so it's probably not an iOS feature.

                            Sidenote: I use PWA all the time, so I'm not totally sure if this behavior is expected with PWA turned off in version 1.4.1

                                Actually I realize this bug made me swear at my iPhone while in fact it was Flarum to blame 😀 I’ve been noticing for some time that editing a Flarum post on my iPhone is very uncomfortable due to the inability to move the caret to the part of text I want to edit. Turns out it’s because the page is scrollable left-right (this very bug) and so instead of moving the caret I’m scrolling the page 🤦🏻‍♂️ Flarum team, please fix this, I’m sure it’s something trivial.

                                Regardless of this issue, is there a way to downgrade Flarum? I also have some other issues on my forum and would like to revert back

                                  hrvoje_hr no, Flarum is not designed in a way that makes downgrading possible. If there was any migrations executed during the update, there's no way to rollback only those migrations. Most Flarum minor updates and some of the patch updates have such migrations. In theory migrations could be implemented in a way that allows rolling back step by step like in Laravel but Flarum has not implemented this feature.

                                  Only solution is to revert to backup, or manually inspect each database change and revert it by hand.

                                  If there was no migration on the other hand (during a patch release or some extension updates) you could simply require an older version of a package with Composer and clear Flarum's cache.

                                  Under some specific situations it would be possible to run an older version of Flarum connected to a newer database version, but that's completely unsupported and likely to lead to errors immediately and/or when finally updating later depending on the kind of database changes.

                                    18 days later

                                    Is a bounty needed for fixing this bug? It really drives me crazy lately and I’m sure it’s probably a CSS one-liner. I’m OK paying a small bounty amount for this being fixed soon because I see no activity in the issue and I’m afraid it might not get fixed for the next release.

                                    2 months later

                                    I’d really appreciate it if you can manage to fix this for 1.7 since it’s one of the only 4 open issues for the 1.7 milestone and I don’t see any activity in it. I bet it’s a one liner CSS or something else that’s trivial, so please, please, please Flarum devs 🙏🏻 It’s a very annoying issue on the iPhone.

                                      cilia as far as I know it will be very soon, probably in a week or two.