Page 1 of 1

Posting Typing Annoyance.

Posted: Sat Apr 30, 2011 1:38 pm
by RoguePhotonic
I don't know how to categorize this problem so I can't really search to see if it has already been discussed.

Often when I am typing a long reply and the box begins to scroll down each letter I type will flick the display back up to a previous line of text which is very annoying to see what your typing and more annoying when you try to highlight anything to edit. Is there a reason or fix of this problem?

Re: Posting Typing Annoyance.

Posted: Sat Apr 30, 2011 2:01 pm
by gary c.
The only solve that I have come up with is to type your post as word doc and then copy and paste it here.

Re: Posting Typing Annoyance.

Posted: Sat Apr 30, 2011 2:05 pm
by ERIC
I'm guessing its something on your end; maybe a browser issue.

Anyone else experiencing the same?

Re: Posting Typing Annoyance.

Posted: Sat Apr 30, 2011 2:06 pm
by rlown
I've seen it, both in IE and chrome. I now prepare my longer posts in notepad.

Re: Posting Typing Annoyance.

Posted: Sat Apr 30, 2011 2:06 pm
by ERIC
What browser and version are you guys using

Re: Posting Typing Annoyance.

Posted: Sat Apr 30, 2011 2:09 pm
by rlown
chrome 11 and IE 8 and IE 9.

Re: Posting Typing Annoyance.

Posted: Sat Apr 30, 2011 3:42 pm
by RoguePhotonic
I'm using Internet Explorer 8.

Re: Posting Typing Annoyance.

Posted: Sat Apr 30, 2011 6:45 pm
by rlown
I just tried jamming about 10 pages of copy/paste into a new topic post, and I could not reproduce the problem. I did find a similar problem on phpBB's forum at http://www.phpbb.com/community/viewtopi ... &t=2122921" onclick="window.open(this.href);return false; which points to another topic there at http://www.phpbb.com/community/viewtopi ... &t=2123849" onclick="window.open(this.href);return false;

I'm thinking if it happens again, we'll just have to try and capture what we were doing at the time and on which post to provide more info.

Re: Posting Typing Annoyance.

Posted: Tue May 03, 2011 7:38 am
by ERIC
My guess would have been a browser conflict with the template, but sounds like it might be more than that. At this time, I'm not sure what can really be done about this issue.