When do you set a transparent resolver to none visible?
I also think if 1 parent (transparent resolver or not) is invisible then the
childs shouldn't be rendered.
Because why else would you set it to not visible?
But i haven't looked deeply into the resolver stuff But isn't it fixable
here:
the transparent resolver is set to non visible in the onClick handler of an
AjaxButton.
ParentResolver is not involved at all.
the problem is, that the transparent resolver is not found in the hierarchy
of the button,
and thus it's not possible to use Component#isVisibleInHierarchy in
is there a test case that fails? (the result should be not rendered but it
does render a bit?)
then i can look into it a bit more, i haven't seen much of the transparent
resolver code.
But are you saying that somebody is setting the transparent resolver to none
visible?
And what component is
On 10/24/07, Johan Compagner [EMAIL PROTECTED] wrote:
is there a test case that fails? (the result should be not rendered but it
does render a bit?)
no, unfortunately, there's not (yet).
then i can look into it a bit more, i haven't seen much of the transparent
resolver code.
But are you
the code is attached to the jira issue
On 10/24/07, Johan Compagner [EMAIL PROTECTED] wrote:
I have to see the code first i think.
Because if the button is not in the hierachy of the transparant container
you could argue that the button needs to be visible. Because what is
invisible?
anybody with more insight into transparentResolvers (matej, igor?):
what is the desired behavior for invisible transparentResolvers?
it's really undefined right now, as the resolver is not rendered, but the
children _are_ (though without markup).
if children of an invisible transparentResolver
