Scroll disappeared
This probably been asked before, but my ability to scroll in the data entry part has disappeared. Is there a way to get it back?
Answers
-
Hi @erutherford
I'm assuming that you are using "Form Entry Mode" and you mean that the scroll bar that allows you to scroll up and down the fields in an entry is either missing (what you indicated) or not responding. Is that correct? And you’re sure that there are more fields than show on the screen - I.e. a scroll is actually needed?
When the controls on the Web Indexing program misbehave for a batch, it might be that your browser needs some "housekeeping" - clearing cache (temporary files) and cookies (tiny files). When something like this happens to me, the first thing I try is to open the same batch in a different browser (Microsoft Edge, Chrome, Firefox, Safari). If that solves the problem, then I go back to my preferred browser and clean it up, which usually solves the problem. If you don't have an alternative browser installed, you can go directly to the "clear cache and cookies" step. See the links below for instructions on this.
The first link warns you that clearing cache and cookies can affect your access to other sites i.e. you might need to re-enter passwords, etc., and suggests a conservative alternative first step to clear just the FamilySearch.org cookies. The second link shows how to do the full cleanup, which may be needed. If these suggestions don't work, come back and post your Batch Code - the letters and numbers starting with M at the end of your batch name (e.g., MXXX-XXX - in case this problem is specific to your batch. Good luck.
https://www.familysearch.org/en/help/helpcenter/article/i-keep-getting-error-messages-when-indexing
1 -
Virginia marriage records in form entry mode. Cleared everything and restarted and nothing. Batch code M36Y-CG4.
0 -
Hi erutherford,
I just used the batch code you gave and was able to scroll up and down through the entry fields. I tried it on both images and had no difficulty. This would indicate that it is not a problem with the batch.
Have you tried opening a batch from different project to see what happens? You can always try one and then if you do not want to index the batch you can Return Batch.
Sorry this isn't much help, I thought John's suggestions would fix the problem.
0 -
I tried two other projects that need scrolling and got the same result, so it's my end. It's a bit of a pain having to use the tab key, but it'll have to do until the solution is found. Thank you both for your help.
1 -
Hi, @erutherford.
I saw another thread where the member was experiencing this. Scrolling up problem
Perhaps there is a bug. I'll be on the lookout for more reports.
For now, please try to clear your cache to see if that helps resolve the problem. I also ask that you share your current operating system and the browsers you've used.
1 -
Hi @erutherford.
Try the "page down" and "page up" keys to rapidly "scroll" the Form Entry panel down and up, respectively. They should be to the right of your function keys. Here is the cluster where those keys are (lower right side) on my keyboard. Sometimes, you might have to poke the page (up or down) key twice, but it's faster than going field-by-field.
0 -
I'm on a Chromebook, so none if those keys exist. Maybe my husband can hook up a Windows keyboard tonight.
0 -
Hi @erutherford
That’s unfortunate
I think that Chromebook has its own operating system (not Windows). While the Windows keyboard might connect and “work,” I don’t know if it will honor the PageUp and PageDown keys. In case it doesn’t, Alt+Up and Alt+Down are supposedly keyboard shortcuts on a Chromebook for those actions . Here is a link to more Chromebook keyboard shortcuts.
1 -
Scroll with two fingers works. Thanks again!
2 -
Nice! You’re welcome.
1 -
My computer geek husband figured it out.
In Chrome, type Chrome://flags. Search for Overlay Scrollbars. Change that setting from "Default" to "Disabled". Restart computer. Once computer is restarted, exit out of, then restart, Chrome browser.
4 -
I love geeks!
3 -
Family Search engineers need to solve this issue for all users. Plain and Simple.
0
