Browser issue XF1 Text Selection issue in iOS 12 Safari


Well-known member
Affected version
I'm not sure if this happened before iOS12, but in iOS12.0 on an iPhone XS Max (guessing others would also reproduce the issue) using XF1.5.22 there seems to be an issue with text selection while posting replies. The video below demonstrates the issue, but essentially you are unable to move the blue selection dots after making the initial selection. This has been consistently reproduced by us as well as some clients, but let me know if you need any more info. is the video link.
I see the same issue on an iPad running iOS12 when visiting a forum I mod for that is running 1.5.x. I tried the same test on another forum running 2.0.x and it does NOT have this issue. I've also not had issues with textarea fields on any other sites I've visited. So this must be something in the Xenforo javascript causing the issue.
I am seeing this too, but I think it might be a browser issue - it also happens at here and here too.

I agree though that it doesn't happen with Xenforo 2.0 - does it use a different editor to 1.x?
i've noticed this as well.

i think if you drag the text selection so there are no spaces at the end it might work again. it can help me when selective quoting.


i have trouble with selective quoting competing with iOS text tools. when i click reply it often doesn't work.
I have a feeling this is a TinyMCE / iOS browser bug and not directly Xenforo. It does the same on TinyMCE’s website.

I wonder why Xen2 is all good though?
XF1 doesn't use TinyMCE either. However, we do use a similar approach in XF1 and that is almost certainly the cause. Unfortunately, that would put this smack in the territory of the browser bug. (Indeed, I don't believe there is any code that tries to take action when doing text selection like this, so that alone pushes me to think browser bug.)

My guess is that this is caused by the use of an <iframe> for the contenteditable area. This is very fundamental to the approach taken, so it can't be changed in 1.x. This isn't the first time we've run into iOS issues that are specific to the use of an <iframe>.

Unfortunately, without an iOS fix, it's likely that the only workaround would be to disable the rich text editor when you trigger this issue (though I appreciate if you're trying to mark up text, that's not helpful).
Top Bottom