UI should not allow to vote on a challenge if that tx is going to fail

[d10r]

I just created a challenge in https://everest.link/project/0xe265942ad988d0c8512a92fac73d124389362191/
Afterwards, I was presented with this view:

The buttons "Keep" and "Remove" are active, so I clicked "Remove", not knowing that creating a challenge already counts as a "Remove" vote (as I now assume).
Next I cloud select a project on behalf of which I wanted to vote. I selected and confirmed.
Metamask didn't complain and let me send the tx. Which then failed: https://etherscan.io/tx/0xb4062ed4048beed1723c2678e2b4f05d0e107a1973be5e02bbc6220480ca19d6

The UI should not allow casting a vote in such a case.

PS: I also wonder why challenges and votes on them are to be expressed on behalf of a project. Why can't I do that simply as a registry curator, independent of a project?

[andromedapool]

Agree on the fact that the buttons should have different states based on the actions that the user took. Also after you vote to keep/remove, the buttons don't reflect this in any manner.

@d10r Regarding to your question, why voting is done on behalf of a project, it is explained in the most recent curator call, link here