Home/ Questions/Q 6552789
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T12:30:11+00:00

I’ve noticed with checkboxes created with the EditorFor method that a hidden input always

  • 0

I’ve noticed with checkboxes created with the EditorFor method that a hidden input always accompanies each checkbox created, and that its value is always set to FALSE. I’ve read a few posts about this on here, and understand that the hidden input is needed, because otherwise no information about the value of the checkbox will be sent at all for an unchecked box during a POST request. (I hope I’ve understood that correctly)

When I look at the Form Data coming out of a POST request, I get the strange (but expected) result that the value of a checked box is both TRUE and FALSE simultaneously: TRUE due to the box being checked, and FALSE due to the value in the hidden input. For example, on the variable “isActive” on one of my forms, I see this in the POST data:

isActive: true
isActive: false

So, which is it? Since it is true before it is false, wouldn’t that mean that the value will always be false since the value of the hidden field will always overwrite the value of the checkbox? The order in which EditorFor places the input element and the hidden element (the hidden one first, and always set to false) just doesn’t make any sense to me. Can someone explain the logic behind this to me?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Editor for model puts them the right way around so that the value of the input box will overwrite the value of the checkbox if it is checked during the mapping. Its not really very mysterious?

    • 0