Cᴏʀʏ Cᴏʀʏ - 1 month ago 4
ASP.NET (C#) Question

Strange behavior using HTML 'readonly="readonly"' vs. JavaScript 'element.readOnly = true;'

Some background

So I was finishing up some enhancements in a web application that does some automatic interpolation of data. There are a handful of textboxes that the user fills out, and other textboxes in between them have values automatically calculated. The textboxes that receive automatically calculated values must be readOnly to prevent user changes, but can't be disabled or they won't get submitted on postback. Each of these textboxes also has a checkbox next to it so a user can consciously check it to make the field writable and thus allow them to override the interpolated value.

The browser: IE 7 (not sure how this behaves in others)

The issue

When setting the
property of the textboxes with JavaScript, the value in the textbox is submitted with the form: I can see it on the server side (ASP.NET) with
and it's in

If I set
on my
<asp:TextBox />
element and don't use the JavaScript method, the value in the text box is NOT available from
(I assume it never made it into the
), but it is getting submitted with the form:
has a value.

My question(s)

What the heck is going on? Is this by design? Is this a browser issue? Did I find a bug? It's annoying that I have to have some extra JavaScript to initially disable the writability of the textboxes when the page loads in order to make my app work.



This is by design. As an ASP.NET security feature, setting it to readonly on the server will keep it readonly regardless of what happens on the client. If you want them to be able override it and actually submit a value then it's not really readonly on the server, only conditionally on the client. You can either do a postback when they check the checkbox to change the readonly attribute on the server, or set only the readonly attribute on the client using this ASP.NET code: