> > Moreover, the new onBeforeRender should be invoked on all components that
> > could be rendered, not only on visible components as it is now...
>
> Could you please explain why you think that is a good idea? I mean use
> cases etc.
> IMHO it is not a good idea. I have seen components that assume some
> state during rendering that is guaranteed to be valid only when they are
> visible.
Well, you are probably right... The only use case when it would be a good idea
is when onBeforeRender would update component visibility. Such invisible
component could not become visible if onBeforeRender would not be invoked on
invisible components.
However, one can always check the visibility state by
if (isVisiblenInHierarchy()) { ... }
but it would be a useless overhead in most cases.
Regards,
Bendis
