Well if that is the case, you could use CSS to make a disabled field look like a text area (set a width, set overflow to true, set the sunken border, set a background and foreground color, etc.)
On 10/14/07, Adam Winer <[EMAIL PROTECTED]> wrote: > There's no skinning property. IMO, Trinidad is absolutely doing the right > thing here. In user interfaces, disabled state should only be used when > there is some way for the user to re-enable the field; in this case, that > is not possible, so plain text is giving the user exactly the right feedback. > > -- Adam > > > > On 10/12/07, Stephen Friedrich <[EMAIL PROTECTED]> wrote: > > My requirements demand some read-only fields that show detail data of a > > selected table row.. > > Currently I have found no other solution than to create setters for these > > fields in my backing bean, even though business logic demands that those > > values will never be changed. > > If I omit the setters Trinidad always renders the values as plain text. > > > > Am I missing some magic skinning property? > > >
