I find the behavior of the watch/collect buttons a bit weird
It goes to the “watched/collected” state, then sort of jumps back and finally returns to the “watched/collected” state. I hope that makes sense.
Same thing happens when you remove plays or remove an item from the collection.
I actually don’t have a problem with this. Some people don’t pay attention to the “toast” notifications that show up at the top of the page. So this seems like a secondary way of showing the “state” of the action being applied.
@CanePlayz I know you’ve provided a ton of feedback on functionality and even design, but I cannot remember if you have a design or development background or not. The functionality of these buttons are pretty industry standard when it comes to “ajaxy” style data manipulation. Other option would always be refreshing the page after each action and that’s just not a good practice for this website because of it’s high amounts of data going back and forth.
I hope that makes a little sense?
I actually don’t have a problem with this. Some people don’t pay attention to the “toast” notifications that show up at the top of the page. So this seems like a secondary way of showing the “state” of the action being applied.
Well that’s the question, is it done or purpose or not.
I know you’ve provided a ton of feedback on functionality and even design, but I cannot remember if you have a design or development background or not. The functionality of these buttons are pretty industry standard when it comes to “ajaxy” style data manipulation. Other option would always be refreshing the page after each action and that’s just not a good practice for this website because of it’s high amounts of data going back and forth.
I’m not yet working in this field but I have basic programming knowledge and know my HTML and CSS at least. 
My question would still be why it’s changing back to the previous state? As far as I understand, you’d have a function for the button that a) sends some sort of request to the server to update things and b) updates the design of the button to account for the new status. But I’m probably missing something here?
On purpose, most likely yes.