"Stories" in "Memories," has a bug, and is overlapping "Audio." Please fix.

LegacyUser

LegacyUser

Don M Thomas said:

LegacyUser

Don M Thomas said:

LegacyUser

Don M Thomas said:

LegacyUser

Tom Huber said: Yeah, I noticed that too, but didn't think much of it. It mostly appears on for a person's memories. where there are photos (which also overlap the next category), Documents (ditto), or as you point out, stories.

This really needs to be addressed.

Windows 7 with Chrome

LegacyUser

Tom Huber said: I was working from memory when I wrote the above. At the present time, only the stories overlap any audio entries. The problem with photos and documents was addressed before this thread was introduced.

The issue really needs to be addressed, if for no other reason than the UI looks really sloppy, like some programmer didn't fully check out the display and considered the code "good enough."

LegacyUser

Beth Ann Wiseman said: Can you reliably reproduce this? Can you give me a person identifier number (PID) and a browser/OS combination that always has this problem? Does the problem resolve itself if you refresh?

LegacyUser

Don M Thomas said: The problem does resolve itself if I refresh, but sometimes it takes more than one refreshing.

This person is showing the problem every time I view his "Memories." I am using Chrome - Windows 10.
https://www.familysearch.org/tree/per...

LATER: Sometimes when hitting on the link I give above, it does not show the problem.

LegacyUser

Tom Huber said: I am running Chrome on a Windows 7 computer. When I first click on the memories for the person James M Martin KJ5W-3XH, the system fails to properly display the stories and the audio sections.

It will correct the display if I refresh the page in the browser.

But, if I go to details and refresh that screen in the browser, and then click on memories, the same screen with overlapped audio and such reappears.

This is a repeatable problem that needs to be resolved.

LegacyUser

Tom Huber said: Still a problem -- using the same person as above, but with Chrome on a Windows 10 computer.

LegacyUser

Beth Ann Wiseman said: This should be fixed now. Let me know if you still see the issue.