You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Eelco Hillenius (JIRA)" <ji...@apache.org> on 2007/10/16 08:39:51 UTC

[jira] Resolved: (WICKET-652) BrowserInfoPage: Couldn't we do this through an AjaxPanel? So we don't have to do that funky redirect?

     [ https://issues.apache.org/jira/browse/WICKET-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eelco Hillenius resolved WICKET-652.
------------------------------------

    Resolution: Won't Fix

I'm closing this, as it is not urgent and tbh I expect that most people will use something custom anyway (like we're doing over here at teachscape).

> BrowserInfoPage: Couldn't we do this through an AjaxPanel? So we don't have to do that funky redirect?
> ------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-652
>                 URL: https://issues.apache.org/jira/browse/WICKET-652
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.3.0-beta1
>            Reporter: Johan Compagner
>
> just a panel that you can add on a page.
> This will render itself (and the form with its textfields)
> does an ajax submit and the ajax submit clears the output..

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