Searching for records in Chrome on MacOS breaks
LegacyUser
✭✭✭✭
johnweathers said: For several months now (possibly a year), when I attempt to search for records on FamilySearch using Chrome on MacOS, the page fails to fully load. The navigation bar at the top renders as does and empty sidebar, but the main section where records should appear only shows the loading spinner. I have looked for problems with Chrome's development inspector and do see some signs of JavaScript and errors in the console:
This problem has been happening for multiple versions of Chrome and multiple versions of MacOS. My current versions are Chrome 81.0.4044.138 (Official Build) (64-bit) on Mac OS Catalina 10.15.4.
Thanks!
This problem has been happening for multiple versions of Chrome and multiple versions of MacOS. My current versions are Chrome 81.0.4044.138 (Official Build) (64-bit) on Mac OS Catalina 10.15.4.
Thanks!
0
Comments
-
Gordon Collett said: I'm just another user on this public feedback board, nobody official at all, but can offer this:
Macbook Pro, macOS Catalina 10.15.4, Google Chrome 83.0.4103.61
Search works just fine:
So it may be something with your system.
Do you have any Chrome extensions or add-ons that could be causing the problem?
Have you completely removed Chrome, gotten rid of every trace of it on your machine including all libraries and preference files, then reinstalled it?
Have you completely removed every trace of FamilySearch from your browser, all history and cookies, to make sure no trace of an old cached version of FamilySearch is causing the problem?
Others here might have other suggestions.0 -
johnweathers said: Thank you! I should have thought of trying that.I disabled all of my extensions and the problem disappeared. Now to try to figure out which one was causing the problem.0
-
Gordon Collett said: Glad I could be of help. When you find the conflict, post it here. FamilySearch engineers do monitor all these posts and I'm sure they will be very interested in whatever you find so they can fix it if it is their fault or be able to notify the author of the extension if it isn't.0
This discussion has been closed.