• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Browser issue OS X Safari Text Selection jump in Editor issue

HWS

Well-known member
#2
Thats Safari specific, has nothing to do with XF. It does that with all HTML editor input fields at all web sites with any software. Just try Chrome and it will work.
 

tommydamic68

Well-known member
#3
Thats Safari specific, has nothing to do with XF. It does that with all HTML editor input fields at all web sites with any software. Just try Chrome and it will work.
Just suddenly? Its never done that before, ever, on any site/ forum I visit.
 

arn

Active member
#4
I was able to reproduce this on my 12" MacBook and iMac. The report of this issue appeared here: http://forums.macrumors.com/threads/i-cant-post-on-macrumors.1946934/#post-22403760

How I was able to reproduce it:

Retina MacBook or iMac
OS X 10.11.2
Safari 9.0.2 - No plugins enabled

Procedure: Go to a thread, scroll to reply box. type in enough text for a scroll bar to appear in the Rich text editor. Tap and drag to start selecting text. The browser page then instantly jumps to the footer. I reproduced this on Xenforo.com

Here's a video. The jump happens quickly, so it's hard to tell from video alone without the accompanying description:

http://f.cl.ly/items/2Y0R090f1j1g1A3y0p0R/weird_jump.mov

I've also had it happen in the EDIT pop-up window, while editing this post. I recently upgraded to 1.5 from 1.4, so it might have been introduced then.

Edit: After upgrading my iMac to latest OS X, it happens on it too.
 
Last edited:

arn

Active member
#8
Thats Safari specific, has nothing to do with XF. It does that with all HTML editor input fields at all web sites with any software.
This isn't true - at least, what's being described here is not typical.

arn
 
Last edited:

HWS

Well-known member
#9
This isn't true - at least, what's being described here is not typical.

arn
Try it at at vB forum or any other editor window at any other software and you will see the same. No matter if TinyMCE or Redactor. The recent Safari does not work well with them.

But that should be solved. I do not know if Apple or XenForo has to solve it. XenForo should try it.
 

arn

Active member
#10
Try it at at vB forum or any other editor window at any other software and you will see the same. No matter if TinyMCE or Redactor. The recent Safari does not work well with them.
You're right it does happen on vB as well.

But it seems Xenforo uses a heavily modified old version redactor, so it falls back on them. I don't think Apple typically provides timely updates on such matters.
 
Last edited:

HWS

Well-known member
#11
You're right it does happen on vB as well.
Not only vB. It happens with every editor input field in every web interface. We experienced it when editing a newsletter in the editor of our newsletter service.

You have to switch browsers to prevent it. I agree it is very unfortunate. Hopefully Apple will provide an update soon.
 

arn

Active member
#12
Not only vB. It happens with every editor input field in every web interface. We experienced it when editing a newsletter in the editor of our newsletter service.

You have to switch browsers to prevent it. I agree it is very unfortunate. Hopefully Apple will provide an update soon.
I tried creating a simple textarea field to simplify it so it would be easier to report to Apple, but I couldn't. I suspect most of those other editors are using Redactor or TinyMCE. You found any examples of simple text fields that it happens in?
 

Chris D

XenForo developer
Staff member
#13
I have been able to reproduce this issue using a fairly common rich text editor set up involving a contenteditable body inside an iframe. I've also been able to reproduce the error on several popular rich text editors including TinyMCE and CKEditor. As this issue is not exclusive to XenForo it suggests a browser bug.

I am in the process of creating a simplified reproduction case to send to Apple and I will update this thread if there are any updates on that. In the meantime, however, this is being marked as a browser issue.
 

KC Riley

Active member
#14
I have been able to reproduce this issue using a fairly common rich text editor set up involving a contenteditable body inside an iframe. I've also been able to reproduce the error on several popular rich text editors including TinyMCE and CKEditor. As this issue is not exclusive to XenForo it suggests a browser bug.

I am in the process of creating a simplified reproduction case to send to Apple and I will update this thread if there are any updates on that. In the meantime, however, this is being marked as a browser issue.
Hi Chris,

Have you received any response back from Apple on this issue with Safari?
 

Chris D

XenForo developer
Staff member
#17
Well, I wouldn't get your hopes up.

I opened a bug report in November 2014 relating to a specific RTL glitch and that was quickly closed as a duplicate. I think it was iOS 9.2 (way over a year later) that it was actually fixed. The annoying thing about duplicate reports though is you can't see other people's reports, and get no updates on reports you've made after they're closed. Still the same on iOS 9.3 beta... maybe iOS 10...
 

KC Riley

Active member
#18
Well, I wouldn't get your hopes up.

I opened a bug report in November 2014 relating to a specific RTL glitch and that was quickly closed as a duplicate. I think it was iOS 9.2 (way over a year later) that it was actually fixed. The annoying thing about duplicate reports though is you can't see other people's reports, and get no updates on reports you've made after they're closed. Still the same on iOS 9.3 beta... maybe iOS 10...
Strange enough Chris, I'm using mobile Safari right now and I haven't run into the issue yet.

I've only experienced the issue with desktop Safari. I'll probably have to put together a notification for my members to let them know to use Chrome and Firefox on their Macs.
 

Chris D

XenForo developer
Staff member
#19
Ugh, my brain is somewhere else at the moment, sorry.

I know this is about OS X Safari but I had iOS in my head for some reason. I managed to trigger something similar with iOS Safari earlier, I wonder if that's a separate bug. I'll need to check that later.