You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Matt Pennington (JIRA)" <ji...@apache.org> on 2011/03/11 02:02:59 UTC
[jira] Created: (WICKET-3523) Inconsistent behaviour of prepending
of startComponent.getId()
Inconsistent behaviour of prepending of startComponent.getId()
--------------------------------------------------------------
Key: WICKET-3523
URL: https://issues.apache.org/jira/browse/WICKET-3523
Project: Wicket
Issue Type: Bug
Components: wicket-core
Affects Versions: 1.5-RC2
Environment: NA
Reporter: Matt Pennington
Priority: Minor
In BaseWicketTester isVisible, the path being checked is not having the start component's id prepended to it. This is inconsistent with isInvisible, which calls out to getComponentFromLastRenderedPage, which does include the start component in the path.
So:
@Test public void shouldFailBecauseThePanelIsVisible() throws Exception {
tester.startPanel(EmptyPanel.class);
tester.assertVisible("panel"); // passes for any visible panel (it searches the path for panel)
tester.assertInvisible("panel"); // throws wicket runtime exception because the panel isn't found (because it searches the path for panel:panel)
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (WICKET-3523) Inconsistent behaviour of prepending
of startComponent.getId()
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-3523.
-------------------------------------
Resolution: Duplicate
Duplicate of WICKET-3465.
It is fixed for RC3
> Inconsistent behaviour of prepending of startComponent.getId()
> --------------------------------------------------------------
>
> Key: WICKET-3523
> URL: https://issues.apache.org/jira/browse/WICKET-3523
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC2
> Environment: NA
> Reporter: Matt Pennington
> Priority: Minor
>
> In BaseWicketTester isVisible, the path being checked is not having the start component's id prepended to it. This is inconsistent with isInvisible, which calls out to getComponentFromLastRenderedPage, which does include the start component in the path.
> So:
> @Test public void shouldFailBecauseThePanelIsVisible() throws Exception {
> tester.startPanel(EmptyPanel.class);
> tester.assertVisible("panel"); // passes for any visible panel (it searches the path for panel)
> tester.assertInvisible("panel"); // throws wicket runtime exception because the panel isn't found (because it searches the path for panel:panel)
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira