Will your components have a fixed underlying component, or will they change depending on the value of the readOnly attribute ? Basically the same question I had for the original suggestion...
Thanks, Grant
Korhonen, Kalle wrote:
-1/0 from me, and I don't mean it as a showstopper, but I think there's an alternative way to implement this. I propose to implement a new "editable" family of components, i.e. editableText, editableTextarea, editableHtml which are rendered either as input controls or as output controls depending on the value of their "readonly" attribute. It solves the semantical problem of rendering inputText as outputText and doesn't add new attributes to components.
Kalle
