Re^2: Inability to UnDo a Vote (prior to executing the actual "vote!"

Replies are listed 'Best First'.
Re^3: Inability to UnDo a Vote (prior to executing the actual "vote!" by kyle (Abbot) on Feb 13, 2009 at 20:23 UTC
The only thing I can think of is that having it there means that a "vote" button click submits something for every node on the page instead of just the ones that will actually do something. I don't suppose filtering out those worthless data makes much difference, but maybe the folks who run the Monastery think differently.	[reply]
Re^4: Inability to UnDo a Vote (prior to executing the actual "vote!" by Anonymous Monk on Feb 13, 2009 at 20:50 UTC
It was suggested in 2003 in Default Null Vote Setting, no one noticed :)	[reply]
Re^4: Inability to UnDo a Vote (prior to executing the actual "vote!" by ack (Deacon) on Feb 17, 2009 at 17:42 UTC
I guess I'm surprised. I would have thought that "Vote" would never enter something for those nodelets that have the "+=0" button selected. I guess I'm dense, but I don't understand why a "no vote" would result in a vote. Seems wasteful to me. I guess I'm just not seeing the "big picture." ack Albuquerque, NM	[reply]
Re^5: Inability to UnDo a Vote (prior to executing the actual "vote!" by kyle (Abbot) on Feb 18, 2009 at 01:55 UTC
I'm not saying an empty vote enters anything into the database. In fact, I'm sure it doesn't. I'm saying, rather, that an explicitly selected "+=0" vote would be sent by the browser for the site to process (into a noop) while not having either "++" or "--" selected does not result in anything being sent. For example, on a page with ten nodes, you vote on one of them. With the default setting, the site receives one selection—for the one node you voted on. With "+=0" present (and selected in nine places), it gets selections for all ten nodes, because that's what the browser sends. I haven't seen the site's code, but I'd be surprised if it doesn't then discard all the "+=0" votes.	[reply]