[ 
https://issues.apache.org/jira/browse/WICKET-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762938#action_12762938
 ] 

Leszek Gawron commented on WICKET-2504:
---------------------------------------

I have found the source of the problem - yet I completely don't understand why 
such an unrelated thing breaks navigation. Probably it is way deeper problem.

I have a FeedbackPanel on my page:

                add( new FeedbackPanel( "feedback" ) {
                        @Override
                        public boolean isVisible() {
                                return anyMessage();
                        }
                });

the markup is:

<wicket:enclosure><div wicket:id="feedback" class="globalFeedback 
ui-helper-clearfix"/></wicket:enclosure>

wicket:enclosure is here for some unknown reasons. As soon as I remove wicket 
enclosure or add some text node inside - the navigation toolbar starts properly 
counting pages (it was showing 0 of 0 before because it thinks it is not 
visible in hierarchy). So to sum it up:

- <wicket:enclosure><div wicket:id="feedback" class="globalFeedback 
ui-helper-clearfix"/></wicket:enclosure> with isVisible overriden for 
'feedback' component causes very weird behavior
- <div wicket:id="feedback" class="globalFeedback ui-helper-clearfix"/> works 
properly
- <wicket:enclosure>blah blah <div wicket:id="feedback" class="globalFeedback 
ui-helper-clearfix"/></wicket:enclosure> works properly

> DataTable's paging broken
> -------------------------
>
>                 Key: WICKET-2504
>                 URL: https://issues.apache.org/jira/browse/WICKET-2504
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.4.2, 1.5-M1
>            Reporter: Leszek Gawron
>
> Current trunk version of NavigationToolbar renders the following:
> Showing 0 to 0 of 0
> followed by :
>  << <   1   2   > >>  (no links here - unable to navigate to other pages)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to