You know how is said that an image worth 1000 words? Here are 600.000 words 
Iām on latest stable iOS - 8.1.3.
8 Likes
Oh wow, thatās brutal.
1 Like
Yeah, I rarely use portrait. Try landscape as a workaround for now.
Well I can confirm iOS 8.1.3 does not fix anything in this area. And 8.2 beta might not either as @BerryBlue noted. If this goes on, we will be forced to include iPad specific workaroundsā¦
I tried with iOS 8.3 beta (Posted: Feb 9, 2015) and the problem still exists unfortunately.
2 Likes
For now, I recommand Mercury browser. 
This works for me pretty smoothly.
Itās because itās using a UIWebView to display web content which is different than what the Safari app uses to render web content.
iOS 8 introduced a new WKWebView which is the same as the Safari app.
FYI I raised this on SO to see if there is a creative workaround
@iamntz -webkit-overflow-scrolling: touch; is pretty terrible performance wise, everything looks super janky. overflow hidden will scroll to top so this has other side effects.
I want to work on this next week, but its not easy. I think a full screen editor at this point is preferable on ios8
5 Likes
You can use it or not. I put it mostly for that momentum scrolling, but should work just fine without that.
From what i read, the performance is bad on iOS <=5, on iOS 6 got performance improvements.
just tried it on 8, super duper janky.
2 Likes
Placed a 500 point bounty
5 Likes
Thanks for making the SO post and adding the bounty @sam!
3 Likes
Guys, I just had an idea which may improve some stuff.
So, right now, the main problem is that when you open up the compose window, the window scroll down past the post, while starts loading stuff (on home page or categories) or just show the related topics (on topics).
So, instead of dealing with all the mess iOS does, what if this kind of info is hidden when the compose is active?
I donāt find the use of infinite scrolling/related posts not even on desktop while the compose is opened (i find it distracting, especially when i want to scroll up to a previous post then quickly scroll down to the latest one).
@sam is going to try to put in a workaround on iPad this week or next week since this bug has persisted into iOS 8.0, 8.1, 8.2 and now, sadly, 8.3.
2 Likes
I have a workaround in place for Safari, grab a glass of wine, a bucket for your tears and read it here:
https://github.com/discourse/discourse/commit/1bdce815e24c175c9f50a6e3b074e569a4a7d6e7
4 Likes
6 Likes
Oh my. That fix is scarry 
1 Like
The crazy thing is that it is enabled by a bunch of very advanced browser features like DOMNodeInserted, and proper handling of preventDefault. I guess we have made some advancement in the hacking department since IE6.
2 Likes
Reply behavior is not good on iPad with thisā¦
Image upload on iPad still very broken as wellā¦ What does this fix do?
1 Like
I focused on iPhone first, will continue tomorrow and clean up iPad.