Re^2: node voting oddity (CGI)

Enable "null vote" in User Settings.

A group of radio buttons with none selected is a violation of some standard but it is still allowed by modern browsers. CGI.pm got updated and decided to enforce this standard on its own. I thought I had patched CGI.pm back to be backward compatible on this point but I guess I missed one of the web servers. I'll fix it shortly and then the problem will eventually go away as Apache children get recycled (I've lost the ability to restart Apache).

- tye

Comment on Re^2: node voting oddity (CGI)

Replies are listed 'Best First'.
Re^3: node voting oddity (CGI) by Anonyrnous Monk (Hermit) on Dec 16, 2010 at 12:52 UTC
I'll fix it shortly and then the problem will eventually go away... I'm still observing the issue (i.e. all '++' buttons preselected after having voted (when having "null vote" disabled)). So, as nearly 3 months have passed by now, I wonder if it has reverted again? P.S.: if it's that CGI.pm is enforcing some (silly, IMHO) standard, how come the inital renderering of the buttons before having voted is not affected by the problem. Isn't CGI.pm being used in this case as well?	[reply]

Replies are listed 'Best First'.

Re^3: node voting oddity (CGI)
by Anonyrnous Monk (Hermit) on Dec 16, 2010 at 12:52 UTC

I'll fix it shortly and then the problem will eventually go away...

I'm still observing the issue (i.e. all '++' buttons preselected after having voted (when having "null vote" disabled)). So, as nearly 3 months have passed by now, I wonder if it has reverted again?

P.S.: if it's that CGI.pm is enforcing some (silly, IMHO) standard, how come the inital renderering of the buttons before having voted is not affected by the problem. Isn't CGI.pm being used in this case as well?

[reply]