Hi,
I would like to add renderedIfEmpty to the t:messages component which
per default is false (current behaviour)
The reason for that: To update/append FacesMessages to a
messages-component after AJAX requests (e.g. PPR)
it has to be possible to locate a DOM element to which this messages
can be
On Tue, 2008-03-25 at 20:50 +0100, Ernst Fastl wrote:
> Hi,
>
> I would like to add renderedIfEmpty to the t:messages component which
> per default is false (current behaviour)
> The reason for that: To update/append FacesMessages to a
> messages-component after AJAX requests (e.g. PPR)
> it has
On Tue, 2008-03-25 at 21:45 +0100, simon wrote:
> On Tue, 2008-03-25 at 20:50 +0100, Ernst Fastl wrote:
> > Hi,
> >
> > I would like to add renderedIfEmpty to the t:messages component which
> > per default is false (current behaviour)
> > The reason for that: To update/append FacesMessages to a
>
Hi,
For t:message and t:messages, there's already a forceSpan attribute, will it
work for you Ernst?
Cagatay
On Tue, Mar 25, 2008 at 11:17 PM, simon <[EMAIL PROTECTED]> wrote:
>
> On Tue, 2008-03-25 at 21:45 +0100, simon wrote:
> > On Tue, 2008-03-25 at 20:50 +0100, Ernst Fastl wrote:
> > > Hi,
Hi,
I like the idea of making that the default behavior. I think for
t:messages it should be save to do
so. As for h:messages I'm not sure how detailed the spec is there.
I'll better check that before
touching h:messages. I also don't know what mojarra does, but I would
guess that they do
the same
I would not recommend forceSpan as an attribute as the use of a span
is renderer specific, not component specific. The component should not
care how the renderer works
On Tue, Mar 25, 2008 at 4:41 PM, Ernst Fastl <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I like the idea of making that the default beha
that would be another advantage of the simple default behavior to
render whatever (ul, table, span, ...) the component usually
renders also if there are no messages wouldn't it?
On Tue, Mar 25, 2008 at 11:51 PM, Andrew Robinson
<[EMAIL PROTECTED]> wrote:
> I would not recommend forceSpan as an att
+1 for deprecating forceSpan and adding generic renderedIfEmpty.
On Wed, Mar 26, 2008 at 1:34 AM, Ernst Fastl <[EMAIL PROTECTED]> wrote:
> that would be another advantage of the simple default behavior to
> render whatever (ul, table, span, ...) the component usually
> renders also if there are n
Hi,
On Thu, Mar 27, 2008 at 1:37 PM, Cagatay Civici
<[EMAIL PROTECTED]> wrote:
> +1 for deprecating forceSpan and adding generic renderedIfEmpty.
does one know if there will be an *empty* for h:message in JSF 2.0 ?
-M
>
>
>
> On Wed, Mar 26, 2008 at 1:34 AM, Ernst Fastl <[EMAIL PROTECTED]> wro
I don't know if they are that specific already - but if we would put
up a JSF 2.0 wishlist in the wiki - maybe even with voting
we could add that idea there and tell the expert group to have a look
from time to time :)
cheers
E
On Thu, Mar 27, 2008 at 2:01 PM, Matthias Wessendorf <[EMAIL PROTECT
10 matches
Mail list logo
