Html.CheckBox returns false if disabled, even if seleced

Hopefully an easy question for you asp.net mvc gurus:

I have a checkbox, created like this:

<%=Html.CheckBox("MyCheckBox", true, new { disabled = "disabled"})%>

In my action I am checking the value like so:

bool isChecked = form["MyCheckBox"].Contains("true");

I expect this to return true, as it is checked. However the hidden element that gets created has a false value:

<input checked="checked" disabled="disabled" id="MyCheckBox" name="MyCheckBox" type="checkbox" value="true" />
<input name="MyCheckBox" type="hidden" value="false" />

First, is there a way to make the HtmlHelper behave as I expect it should? Or is manually constructing the input/creating my own 开发者_Python百科helper method the only way? (not that this is a big deal...)

Second, can anyone shed some light on why the checkboxes behave this way? Am I incorrect in assuming a disabled checkbox that is ticked should == true? Does a disabled state semantically mean false?

An input field marked with the disabled="disabled" attribute NEVER sends its value to the server. If you want to achieve this you could use the readonly="readonly" attribute which still prevents the user from modifying the value but sends the existing value when the form is submitted.

I don't know if it solves your problem but this was the solution for me:

My model has an UserMigrated boolean property, once the user has setted to migrated, he can't go back, so the view becomes:

@if (Model.UserMigrated)
    {
    <td>@Html.CheckBox("chkBoxReadOnly", true, new {disabled = "disabled"})</td>
        @Html.HiddenFor(m => m.UserMigrated)
    }
else
    {
    <td>@Html.CheckBoxFor(m => m.UserMigrated)</td>
    }

1) From my point of view there is no way to change the behavior of the Html.CheckBox method. I had to face the problem time ago and i ended up with manually constructing the input checkbox as you suggest. To construct the input checkbox is not always the hell as using the helper methods is not always the eaven. Of course biulding your own helper method can be the right choise.

2) Disabled input field is not posted when form is submitted; i would expect the same, submiting disabled input checkbox fileds, whether are checked or not.

We can argue about the choice adoped to relay on input hidden field for pushing into the request the checkbox, when the checkbox is not selected. The side effect of this choice is that we will find the checkbox name among the the posted data even if the checkbox is disable in disagreement with what stated above that is: disabled input field is not posted when form is submitted

Adding the Hidden field before check box worked for me. Note that i am adding the hidden field only if the field is disabled.

Credit goes to this post

  @{
     if (Model.MyFieldDisabled)
      {
         @Html.HiddenFor(x => x.MyField)
      }
   }    

    @Html.CheckBoxFor(x => x.MyField,  new {disabled = "disabled"})

I faced a similar issue when trying to use disabled for a checkbox. My solution was just to not display the checkbox since the user did not have the access to modify the field.

I also made sure the Html.HiddenFor was there so the value was retained.

In my case below was the scenario, it was to do with asp-tag helpers. So to send the value, I have used input hidden fields and it worked.

<input type="checkbox" asp-for="@Model.SomeList[i].Selected" disabled />
<input type="hidden" asp-for="@Model.SomeList[i].Selected" />

HTH to others :)

@(Model.IsClosed ? "Yes" : "No")
@Html.HiddenFor(m => m.IsClosed)

This worked for me in all cases. No need of disable and readonly