@tsteur opened this Issue on September 2nd 2020 Member

refs https://github.com/matomo-org/matomo/issues/16368


when calling .dropdown


then it fails here:

Noticed this in ?module=CoreHome&action=index&idSite=1&period=day&date=yesterday#?idSite=1&period=day&date=2019-11-28&segment=&category=Goals_Ecommerce&subcategory=MultiChannelConversionAttribution_MultiAttribution

when I selected an attribution model


I can't reliably reproduce it so far though and things seem to still generally work so we may be able to ignore it for now. Might be some race condition or so.

@diosmosis commented on October 20th 2020 Member

@tsteur I think I found the issue here, it fails if a datatable is loading, and before it finishes loading, we re-load the datatable in some way. So:

1) datatable is starting to reload because of some change (eg, attribution dropdown changed)
2) before datatable is finished reloading, another dropdown is used, causing new reload
3) since the content for the first datatable reloaded is never added to the dom (or is added and replaced w/ a loading gif), the dropdownConfiguration dropdown fails to find a specific element, causing it to throw

not yet sure if there's a quick fix

@diosmosis commented on October 20th 2020 Member

found a quick fix

This Issue was closed on October 20th 2020
Powered by GitHub Issue Mirror