The discussion revolves around a UX issue where the reply box on mobile is initially too large, making it difficult to access buttons like preview. seanblue reports the problem on iPhone 8 with iOS, noting the box size changes after the keyboard is closed. awesomerobot confirms the issue on Meta, suggesting a regression. sam explains the root cause lies in iOS keyboard handling and mentions the upcoming Visual Viewport API as a future solution, though it’s not polyfillable. j.jaffeux confirms the API is iOS 13+ only. sam humorously notes the app could polyfill it but considers it cheating. seanblue asks for a fix, and sam suggests waiting for iOS 13 for a proper fix, with possible interim hacks.
When you first start a reply on mobile, the box is too big. This makes it so you can’t easily click the preview button in its new location (or the other buttons in the row). I’m using iPhone 8, latest iOS, with the stock iOS English keyboard.
Reply box right after clicking reply to an existing post:
There’s something inconsistent happening. I see the problem if I click reply and the input gets focus right away, but often after clicking reply the input isn’t being focused… seems like something may have regressed?
Oh now I know why I never notice this, I use the app and we have enough extra space in the app never to notice this issue if it even happens.
Thinking out loud here…
On iOS 13 with visual viewport api we are going to be able to eliminate the entire ugly iOS hack (and much of the iOS physical keyboard hack)
In the interim I guess we can adjust some numbers in the hack.
The last changes in the safari hack file came from @j.jaffeux who added mutation observer and shuffled a bit, can you investigate this Joffrey and see if you can repro and correct it?
Another thing to think about is that we can live in the future with the app, cause it can simply provide a simulation API so we get a non hacked up pixel perfect fit. Not saying we do this right now @pmusaraj but something to think about depending on how good visual viewport api ends up being.