Madrugada
Since: Jan, 2001
Stratadrake
Dragon Writer
Since: Oct, 2009
#7: Sep 15th 2011 at 6:46:09 PM
^ Second that: Make it an option on the Lock button itself. Lock both when you need to, or just one when you don't.
edited 15th Sep '11 6:46:35 PM by Stratadrake
An Ear Worm is like a Rickroll: It is never going to give you up.
Madrugada
Since: Jan, 2001
Stratadrake
Dragon Writer
Since: Oct, 2009
#9: Sep 15th 2011 at 7:41:19 PM
I can only guess, but I'd rank it as a "not very". The functions for locking a topic and locking a crowner are already defined, so it's conceptually simple to do both in a single client request. Now if the existing lock-topic button brings up a confirmation form instead of simply locking it NQA, adding an extra option onto the form is just an HTML checkbox that the server can detect easily and act appropriately on.
An Ear Worm is like a Rickroll: It is never going to give you up.
Total posts: 9

As shima has pointed out to me twice now, crowners don't lock when the thread they're hooked to is locked, which could conceiveably cause a problem with someone trying to scam votes. Can the system be changed so that locking a thread auto-locks its crowner?