Last post May 15, 2006 01:10 PM by vinaybaliyan
Nov 18, 2005 02:46 AM|Joost van Schaik|LINK
the 'parent' page, this value nicely goes to the server. A really useful feature, especially if the value displayed needs to come from a pick list.
Now in ASP.NET 2.0 SOMEONE thought it a really good idea to make read-only textboxes REALLY readonly. Just before the postback I see the textbox being reverted to it's former value - obviously a feature of the new and improved postback client script. Maybe
someone thought it bad security to be able to change a read-only textbox by scripting. But the only way I now seem to be able to keep my data passing trick to work is to set the textbox readonly property to false. But THIS enables the user to select the textbox
and tamper with the value selected by the popup WITHOUT the need of scripting!
Now what? Of course there's a way around this, by using a second (hidden) writeable textbox for the real value and a read-only textbox in sync with the display value, but hey Microsoft, that means I need to convert a lot of controls I designed the last few
years. Is there no simpler way around this? Does anyone know how to turn off this 'feature'?
Apr 27, 2006 11:56 AM|chris_sisler|LINK
Has anyone found a work around/solution for this?
Apr 27, 2006 02:39 PM|chris_sisler|LINK
Please see the following post for more:
May 15, 2006 01:10 PM|vinaybaliyan|LINK
In ASP.NET 1.1 , if you make any text box as readonly, user can't enter value but thru code you can set the value.
In ASP.NET 2.0, if you make any text box as readonly, use can't enter value even thru code you can not insert the value. So dont set ready only property instead use contentEditable=false attribute to get the same behavior as in .net 1.1