...en calling removePlugin
[#1317] Fixed issue where trackevents were not being removed properly…
… when calling removePlugin
Are you sure this should be reversed?
I worry this was here to make sure if the currently indexed track event is removed, we are not forced to scrub forward and back to be able to get the proper index.
So yes, I am pretty sure you want to keep the old code, being <=
You also probably want to make sure it never goes below 0. If it currently is 0, and you're removing the first three track events, you want to keep it at 0, otherwise, you want to go back one.
Need some tests to prove it :)