Saturday, September 15, 2018

MedBetterDNA extension update double filters to 8 each

MedBetterDNA has been updated to version 3.0. 

By user request, the Chrome extension MedBetterDNA, used for actively filtering AncestryDNA results (and showing notes on the main results page) has been updated to version 3.0, supporting eight hashtag filters for "show only" and "remove all" filters. This is double the previous maximum of four hashtag filters. Note that using more filters may increase time to fully process a Results page.

In anticipation of future similar requests, please also note that further increasing the number of filters isn't simply a matter of pumping up a number in the extension code. The extension is pushing the limits with the current code structure, and adding more filters in the future, if ever, will likely require significant rewrites to large portions of the extension's program code. I'm not saying it won't ever happen, I'm saying it won't happen soon or easy.

Post to support if you experience problems with the update or extension operation.


  1. No Trees are showing on page when Show No Family Trees option is unchecked since Ancestry’s update to show Unlinked trees

    1. Unfortunately browser extensions such as MedBetterDNA are basically at the mercy of the website to provide information, and when it is removed, it can't provide functionality based on the removed information. I'll update the extension to hide the filters which no longer apply to the site change.

  2. The option "show No Family Trees" no longer filters out matches without trees. I suspect that changed when Ancestry starting showing the tree status (no trees, unlinked trees, etc.) on the main match page.

  3. Yes, the site's last update broke the tree-based code. I might be able to correct for the changes, but the tree information display is unstable on the site for me, usually showing a loading image on the results page and never finishing to show the actual information. Once in a while I get a fully loaded page with the information, but it's uncommon enough I can't reliably test for it.

    As a consequence, I will probably remove the inoperative tree-based filtering for next update until the site stabilizes.


Please note that comments will not be visible until they are approved by a moderator.