Hi,

 

I know why your thinking it is wrong, but the problems is that when you set the readonly attribute on the <xp:inputText> control it does not just a pass through to the readonly attribute on an input control.....It works like you discovered, it changes the rendered html to a <span>  This is how it works inside of xpages, for instance if you have a form bound to an xpage and change from edit mode to read only it changes those from input's to span's  This is the way the control was coded to behave.  As you found you can always use client side javascript to change the readonly attribute if you need it changed.  I actually like the controls dual rendering functionality I think the span looks a lot nicer than an input box with a readonly attribute set to yes. Also you can style the two differently even though they are the same control without using css3 selectors.  You could create a new renderer for the control that would allow you have your read only attribute work like you want, but maybe overkill for what you are needing.

 

Thanks
-Toby

Thanks Toby for the explanation. Atleast now I know this is not possible via property.

 

But you should note the help popup for the readonly property - "Indicates whether or not this control will prohibit changes by the user. This control may receive focus unless it has also been disabled."

 

Now you know the source of my confusion...  :)