It’s merged in Discourse main branch, so now it depends of how you update.
1 Like
Any chance the fixes may still make it to stable? 
It really should, even though the devs actively discouraging using stable. This behavior makes discourse nearly unusable on iOS. It’s as bad as it gets.
1 Like
I will look this week if I can backport it, might not be super easy but will try.
4 Likes
I didn’t forget this, but this is not stable enough for me to backport, I still have been doing fixes as of today. Im working a lot on a better and more longterm solution, so we can be more prepared to Apple/iOS deciding to break everything.
8 Likes
iOS 26.2 just got released and from a quick check, I could no longer reproduce this issue (or any other) — not even on stable which is what we use. I checked both with the the Discourse app and Safari, if relevant. Did Apple finally nailed the issues with Safari?
6 Likes
Yes. I will close this, and don’t take this as I don’t care, I literally lost 3 months of my life to Apple deciding to break everything, but… there are mostly 3 cases:
- we could do a fix and we did it
- we couldn’t do an immediate change and are working on it
- there’s nothing we can do until Apple fixes it
Anyways, afaik, it’s mostly working correctly on 26.2. There are few problematic modals + keyboards situations, but we should have a solution for this in January.
9 Likes