I was aiming for checking there wasn’t bug in the topic / post reading logic.
However this might actually be considered a bug…
I consider “dismiss” a “dangerous” operation from a users reading point of view…
In so far as you can “dismiss” topics you haven’t seen yet.
Topics or posts have been created in the between loading the list of unread topics and confirming the dismiss can be incorrectly dismissed.
Yes, possibly a small window - but with users leaving browser windows open for days now - it might be bigger than you first think.
In the same way as a delete operation takes the exact topic / post ID’s and passes those to the server “dismiss” should so the same…
… only dismissing those topics that were in the view when the user selected “dismiss”.
Currently it just passes:
So no ID’s - meaning - everything is dismissed regardless of if the user was aware of it or not.