I’m sorry if it turns out to be something wrong at my end, but here we go, on Firefox 68.6.0esr just now.
Using only keyboard navigation, starting from a freshly opened main page https://meta.discourse.org/ in a new tab, I have no tracked topics at the start.
I press ‘j’, ‘Enter’ to enter a topic.
I press ‘j’ enough times to the suggested topics, press ‘Enter’ to enter one of them.
I press ‘j’ ‘m’ ‘t’ - now I am tracking both this topic and the one entered from the main page.
BTW, I just noticed that when in step 3 I pressed ‘m’ ‘t’ immediately, only the correct topic was tracked. But even after that pressing ‘j’ ‘m’ ‘t’ changed the state of the previous topic.
So I couldn’t repro this exact bug and neither can @david, but @david had a lot of requests going on in his browser, which I didn’t have, first thought was browser and then multiple browsers opened?
After some search I understood it was coming from browser size (which was narrow for me and large for David) and the topic time line button which kept registering new appEvents handler was shown for David and not for me.
I think this should greatly improve the situation on topic tracking, more details in commit:
Ah, yes, requests. So at the end the procedure above generated two identical POSTs to https://meta.discourse.org/t/146924/notifications and then the I guess problematic one, to https://meta.discourse.org/t/113192/notifications.
@joffreyjaffeux Thanks. In a couple tries I could no longer reproduce the problem here and indeed I always see only one and correct request to /notifications now - no duplicates and no requests for other topics.