You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Johan Compagner <jc...@gmail.com> on 2007/05/24 18:54:57 UTC
Re: [jira] Updated: (WICKET-271) investigate Ajax back button support
this wont be fixed for 1.3 at least i dont think so, we have support
for it on the serverside but no support on the client side yet
On 5/24/07, Alastair Maw (JIRA) <ji...@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/WICKET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Alastair Maw updated WICKET-271:
> --------------------------------
>
> Fix Version/s: (was: 1.3.0)
> (was: 2.0)
>
> > investigate Ajax back button support
> > ------------------------------------
> >
> > Key: WICKET-271
> > URL: https://issues.apache.org/jira/browse/WICKET-271
> > Project: Wicket
> > Issue Type: Improvement
> > Components: wicket
> > Reporter: Eelco Hillenius
> >
> > Investigate what we can do to support the back button with Ajax.
> Currently, we don't support versioning with Ajax, so the back button always
> takes you back to the location before the ajax calls.
> > See discussion here:
> http://www.nabble.com/Single-page-applications%3A-bad-idea-in-Wicket---tf3182341.html
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
Re: [jira] Updated: (WICKET-271) investigate Ajax back button support
Posted by Johan Compagner <jc...@gmail.com>.
ahh i did read it wrong, maybe its my small screen (nokia 9300 with
mobile gmail application)
On 5/24/07, Al Maw <wi...@almaw.com> wrote:
> Johan Compagner wrote:
> > this wont be fixed for 1.3 at least i dont think so, we have support
> > for it on the serverside but no support on the client side yet
>
> Yep, that's why I removed 1.3.0 from the fix versions. ;-)
>
> Al
>
Re: [jira] Updated: (WICKET-271) investigate Ajax back button support
Posted by Al Maw <wi...@almaw.com>.
Johan Compagner wrote:
> this wont be fixed for 1.3 at least i dont think so, we have support
> for it on the serverside but no support on the client side yet
Yep, that's why I removed 1.3.0 from the fix versions. ;-)
Al