Does your browser jump around when editing a profile?

Question

I can't imagine what's causing this; it happens in both Chrome and Edge.

When I'm editing some text on a profile and hit enter, the browser jumps so far down the page that I am either not seeing the edit box, or I'm down at the bottom of it and have to scroll way up the page to get where I was editing. This happens a lot, it is a time-waster, and very annoying.

Does this happen to anyone else? If so, did you fix it?

Comments

Do you have any browser extensions enabled when this is happening? If so, could you please try disabling each of those extensions, one at a time, and checking whether the behaviour changes as a result?

---

Yes Murray, I have 3 running: Sourcer, Bee and WBE. I will try disabling each, one at a time, to see if anything changes. Thanks for the suggestion.

---

Yes, it happens to me. But it was happening before I started using extensions so I don't think disabling them would make a difference. It happens most often when I paste text, such as a source citation, into the edit box. You're right, it is annoying to have to scroll back up and find my place again.

---

I just had similar occur when I removed a block of text.  The page scrolled right to the bottom of the preview screen, and I had to scroll all the way back up to the edit box to paste my block of text to a different position on the page.

I was using Edge browser, and the only extension (not in use at the time) I have is Sourcer.

Answer 1

Yes. I can't stand the bouncing.

Answer 2

Yes I see something like this when editing in Chrome and it is annoying. I don't know of any way to fix it.

I tried experimenting a bit just now. I don't see it ever scrolling such that the text edit cursor is off the screen (which it sounds like you do).

What I'm seeing in a few experiments is this:

The first time I hit Enter in the text area, if (and only if) the top of the text area is not visible due to the page being scrolled, then it scrolls both the page and the text within the text area so that a) the top of the text area is at the top of the window and b) the line with the text cursor on it is the first line visible in the text area. This means that you can't actually see the line that you just typed (before hitting Enter).

Answer 3

This happens to me with Safari on my iPad as well.

Comments

I also see jumping of position when editing profiles on my iPad using Safari. This is definitely caused by the WikiTree Browser Extension. It never happened before I started using WBE. It's mildly annoying, but the other benefits of WBE compensate.

---

It may be possible to stop the jumping by turning off the WBE option

Edit Profile > Change Summary Options > Show the options and save button in the right-hand column

See

https://www.wikitree.com/wiki/Space:WikiTree_Browser_Extension#Change_Summary_Options

https://www.wikitree.com/g2g/1617261/the-wikitree-browser-extension-now-available-macos-and-ios?show=1621857#a1621857

---

Jim, I'm trying that. I just turned it off.

Thank you

Answer 4

Re: Curser jumps around. I use Chrome browser and obtain the WikiTree Sourcer Extension from the Google Play store. I also use a small number of additional extensions such as .pdf. I've been experiencing the curser jumping bean effect for about a month but have been living with the problem.

I removed all extensions from the Chrome browser and reinstalled the WikiTree Sourcer extension. The problem hasn't gone away. I just lost 1/3 of a page of new text on a profile I was editing and the handy-dandy automated Draft File save function saved the new (text deleted) version before I could blink. Fortunately, the Preview pane window, which contained the text accidently deleted, was still open. Whew. I copied that text back into the profile edit mode in order to restore the profile being edited. I then uninstalled the Sourcer extension. Looks like I have to teach myself a quick way to use the Ancestry sharing link template.

Answer 5

Yes, this happens to me using Safari on my iPhone with no extensions.  I suspect that it is related to the autosave feature.