fetchcomms wrote:

I sometimes have this issue while editing in portrait mode (not landscape) on an iPod Touch running iOS 4.0. It has never occurred on an iPad or PC in any browser.

thor.malmjursson wrote:

(In reply to comment #0)

Further to the original report and details on the Village Pump at Commons, I can now confirm this bug is occurring in 3 separate browsers, each unrelated. As well as the initial report against Firefox 3.6.13 in KDE 4.4.5 (Mandriva 2010.2), I'm also experiencing this issue in Opera 10.1.63 (same DM and OS) and also in the Chromium browser.

The error ceased in Konqueror (the fourth one I have), after turning off Javascript, but not in the other three.

I can't reproduce this using Opera 10.10 or Firefox 3.6.13 under Ubuntu. It appears that this is not a Wikipedia/MediaWiki bug

thor.malmjursson wrote:

I'd beg to differ I'm afraid. It's been seen across 3 different OS's, 4 different browsers, PCs, Laptops and iPods, and unless something very drastic has happened, we can't all have the same problem wrong with our equipment :)

I count two OSes: iOS 4.0 and Mandriva. Is there a third?

I can try out Mandriva or other Linux variants and Windows Vista personally and, if we need to I can get someone else to try it on another OS. (And I see from the village pump link that Trevor is already taking a look but has been unable to reproduce it.)

Is there anything more than "editing text at the bottom of the large pages like BarkingFish's user talk page" that we can use to track this down?

(giving to trevor since he has looked at it and been unable to duplicate.)

In a couple minutes poking around at User talk:BarkingFish in Firefox on a Mandriva 10.02 live CD, I wasn't able to reproduce the jumping behavior. I tried anon editing (default Vector skin & enhanced editing toolbar), and logged in as myself switched over to Monobook skin & old-style edit toolbar to match the sample video.

I do recall vaguely that textareas scrolling unexpectedly to the top is a thing that happens; I think there are workarounds in some of the edit toolbar code for instance, as changing the text contents can do this in some versions of some browsers.

However, when just typing in with the regular classic editor, that shouldn't be happening...

Thor, do you still see the problems if you edit without logging in, or on a freshly created account? Do you have any gadgets enabled? Browser extension issues are unlikely if you're seeing this on several different browsers on the same machine; but something specific to your wiki accounts might be. Could be something that's triggering something as a side effect...

thor.malmjursson wrote:

Brion, I've not honestly tested it with a brand new account, so I'll set a new one up and have a shot. The video was done at commons so I'll try and do a new test account and run it through there. I do have several gadgets on, but nothing at commons other than TinEye. I'll see where it goes. And for the record, yes I do see this problem when not logged in.

Now...

(In reply to comment #5 by Mark A Hershberger)

I count two OSes: iOS 4.0 and Mandriva. Is there a third?

Yes there is. If you refer to the text of the discussion which started this on Commons Village Pump, located here:

http://commons.wikimedia.org/w/index.php?title=Commons:Village_pump&oldid=48188606#Problems_with_standard_wikim.28p.29edia_text_editor

You'll notice that the OP, Jarekt, was on Windows XP with Firefox. So that makes iOS 4.0, Mandriva and Windows XP.

Did you test with a new account yet? Also see Bug #25830 although I don't think this is related to live preview.

thor.malmjursson wrote:

Really sorry, Mark, but I've been as busy as stink doing some investigative reporting for Wikinews, and also had some surgery, so I've been quite tied up. I will create a new account *now*, right this very minute, and drop back with some comments on whether this is still occurring afterwards.

Bearing in mind there's been an MW software upgrade to 1.17wmf1, and this was reported for 1.16.0, I'll see whether the upgrade has fixed it, or not.

Back in a while :)

thor.malmjursson wrote:

New account is in place at Commons, http://commons.wikimedia.org/wiki/User_talk:FishingBark_TEST

I have edited in the same conditions as when I placed the report, full text box, etc, and I am noting no errors at this time, no jumping, flickering text in the edit box, zip.

At this time, I'm not sure whether it's the 1.17wmf1 upgrade which has done this, or the new account, but either way, I am now able to return to wiki editing in the normal manner, instead of using KATE :)

Fletcher, are you still having the problem?

I'm not going to close this just yet, but I'm glad you've found relief, Thor. :)

fetchcomms wrote:

Nope, works fine now.

thor.malmjursson wrote:

Now we just have to wait for the OP from the Commons village pump. I'll try and attract his attention, and see if he can post here. If not, I'll get him to post on his talk page at commons and transfer his comments in if that's acceptable :)

thor.malmjursson wrote:

(In reply to comment #14)

Now we just have to wait for the OP from the Commons village pump. I'll try and
attract his attention, and see if he can post here. If not, I'll get him to
post on his talk page at commons and transfer his comments in if that's
acceptable :)

Done this, see http://commons.wikimedia.org/wiki/User_talk:Jarekt#With_regard_to_the_text_editor_bug_.28Village_pump.29

Hopefully, he'll get back to us asap.

I initialized discussion at Commons Village Pump about issues I had with the editor and which is mentioned in the discussion above (http://commons.wikimedia.org/w/index.php?title=Commons:Village_pump&oldid=48188606#Problems_with_standard_wikim.28p.29edia_text_editor ). However I am not sure if the problem I described is related to this bug report. I was complaining about random/unexplainable jumps of the typing cursor to come other locations while typing. I had a problem with that for a while but I do not think I noticed it in last week or two.

thor.malmjursson wrote:

That is the same bug, Jarekt - I and at least one other editor were experiencing the same thing. If you're not noticing it anymore, that's a good thing. It means this could be classed as Resolved. If you could just check it, and positively confirm it's gone, we're good to close this :)

It is hard to confirm, in my case it was happening only occasionally, but I had over 200 edits in "last week or two" and I do not remember seeing it.

thor.malmjursson wrote:

Appears fixed by the distribution of 1.17wmf1 - no futher reports, issue closed.