AFAIK, the "submit" method utilized is irrelevant. The problem comes from POSTing HTML combined with the useful Domino behavior of not sending every field is sent to a browser. Given that some fields may not be sent to the user to edit, Domino does not clear out "non-submitted" fields. Example:
- document contains a computed Readers field. That field is not sent to the browser as an input field. Consequently, upon submit, the browser does not POST that field. Clearing that readers field simply because it wasn't POSTed by the browser would be wrong.
Well, what happens with an completely cleared out checkbox field? Nothing is posted/submitted. Again, Domino doesn't clear it out (or didn't prior to the fix highlighted by Jake).
Thanks for the news that this is taken care of in 6.5.5 & 7 Jake. I presume the same is true of radio buttons (clearing those requires JS... ;-)
@Dorian and @Jerry
Time to take another step back...
AFAIK, the "submit" method utilized is irrelevant. The problem comes from POSTing HTML combined with the useful Domino behavior of not sending every field is sent to a browser. Given that some fields may not be sent to the user to edit, Domino does not clear out "non-submitted" fields. Example:
- document contains a computed Readers field. That field is not sent to the browser as an input field. Consequently, upon submit, the browser does not POST that field. Clearing that readers field simply because it wasn't POSTed by the browser would be wrong.
Well, what happens with an completely cleared out checkbox field? Nothing is posted/submitted. Again, Domino doesn't clear it out (or didn't prior to the fix highlighted by Jake).
Thanks for the news that this is taken care of in 6.5.5 & 7 Jake. I presume the same is true of radio buttons (clearing those requires JS... ;-)