When sending multiple names requests from explore your area by quickly clicking on different group names, there appears to be an low frequency use case not handled.
I suspect it looks like this:
name request A has a large response can no longer be cancelled and is in the processing loop.
name request B is clicked.
name request B responds before 1 is finished.
name request B processes and writes the new names list to the DOM.
name request A processing loop finishes and overwrites the names list in the DOM.
Address this with the introduction of a new variable to keep track of the last name request and match this before writing to the DOM. Any existing names list might need to be removed again.
When sending multiple names requests from
explore your area
by quickly clicking on different group names, there appears to be an low frequency use case not handled.I suspect it looks like this:
name request A
has a large response can no longer be cancelled and is in the processing loop.name request B
is clicked.name request B
responds before1
is finished.name request B
processes and writes the new names list to the DOM.name request A
processing loop finishes and overwrites the names list in the DOM.Address this with the introduction of a new variable to keep track of the last
name request
and match this before writing to the DOM. Any existing names list might need to be removed again.