Hi Adam,
perhaps I should be a little more speicific:
We want to be able to delimit the length of the outputText's text (so that
long text's won't
break our pages' layout). The way we came up to achieve this was to have
something like
display: block;
overflow: hidden;
in our CSS. Without this CSS-tweaking above, a width definition via the
inlineStyle attribute
has no effect (as you'll surely know; I just mention it for those of us
lesser experts...).
If the text now gets longer than the "inlineStylish" width, it still can be
accessed
by/presented to the user via the tooltip (shortDesc).
Thus, we enhanced the OutputTextRenderer to be styleclass-aware and to set
the tooltip
accordingly (if no other tooltip is defined).
Do you consider this to be contrary to the "intended spirit" of the
outputText (eh, or even
weird) or is this approach OK?
Thanks,
Carsten
Adam Winer wrote:
>
> Generally speaking, you don't want to do this for
> outputText: you want to style parent components
> and/or the default font of the skin, not the outputText
> itself.
>
> -- Adam
>
>
> On 8/10/07, Carsten Pieper <[EMAIL PROTECTED]> wrote:
>>
>> OK, thanks for the speedy answer!
>>
>> So it look's we should build our own renderer...
>
--
View this message in context:
http://www.nabble.com/-Trinidad--Skinning---no-CSS-selector-for-tr%3AoutputText--tf4247489.html#a12121153
Sent from the MyFaces - Users mailing list archive at Nabble.com.
