Hints not reliably removed from Research Help list after they have been attached to the profile
When the "new" source linker was implemented several years ago, one of the improvements was to remove a hint from the Research Help list once the source had been attached. Previously, an attached hint remained in the list in the profile screen from which the source linker was opened, and you had to refresh the profile screen to remove the hint from the displayed list. With the improvement, the hint is removed as soon as the profile screen gets focus again after the source is attached; normally that is when the source linker is closed. The same behaviour applies if you use the descendancy view to find and attach hints.
So, as of today, I have found that this removal behaviour has become erratic. Now, the hint will more than likely remain in the list after it has been attached and the source linker has been closed. Just like the old days. If I reopen the still-visible hint in the source linker, it is shown to be attached as I expect. But when I close the source linker without doing anything other than look at the screen, the hint disappears from the list.
This behaviour occurs in Windows 10 with Chrome, Edge and Firefox browsers.
Answers
-
I had a hint this morning that was not a match - similar name but different family. I had to decline it with reasons THREE times before it was removed from the list.
0 -
I've been running into the same problem, but it seems like it's just a long delay before the decline goes through.
0 -
What happens if instead of opening the source linker again or instead of clicking decline three times, you refresh the browser window three or four times?
0 -
I refreshed several times before I resorted to declining multiple times. There were definitely website issues yesterday. Haven't checked yet today, but my Contributions list was all out of whack yesterday.
0 -
Ah, OK. I saw the same the same issue but refresh would work for me eventually, but it did — and still does take about 5-10 seconds for FS to "recognize" the decline.
I am seeing a scary situation where profiles previously marked Not a Match are being suggested as possible matches. If you click on them it even says that it was marked as Not a Match. This is in addition to it being difficult to mark something as Not a Match, which a few people were seeing yesterday.
0 -
The Android Family Tree app is behaving in a similar way when sources are attached.
0 -
Is this an issue similar to the one recorded at
whereby a user's action is not being picked-up by the system?
1 -
This has been happening to me too!
0 -
The "rejecting possible duplicates not working" has been resolved. Please let us know if it has already resolved the original concern mentioned here since they were probably related.
1 -
The original issue of the record hint not being removed from the displayed list in the profile page or tree view seems to have been resolved. Thank you.
0
