[
https://issues.apache.org/jira/browse/WICKET-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hendy Irawan updated WICKET-5290:
---------------------------------
Description:
I wonder if Wicket 6/7 has or planned for good history API support, i.e.
navigable ajax updates a la Twitter/Facebook?
If not then I'd like to propose... It'd make Wicket not only very relevant but
a breakthrough in a *post*-HTML5 world.
Originally posted at
https://issues.apache.org/jira/browse/WICKET-3813?focusedCommentId=13720564&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13720564
[~mgrigorov] responded:
> Do you know of a good JS History library ?
> All I have tried have issues for different browsers.
What I ever used is Backbone. Which is a great all around library.
Snippet from http://backbonejs.org/#Router :
<blockquote>
Web applications often provide linkable, bookmarkable, shareable URLs for
important locations in the app. Until recently, hash fragments (#page) were
used to provide these permalinks, but with the arrival of the History API, it's
now possible to use standard URLs (/page). Backbone.Router provides methods for
routing client-side pages, and connecting them to actions and events. For
browsers which don't yet support the History API, the Router handles graceful
fallback and transparent translation to the fragment version of the URL.
</blockquote>
Breadcrumb components would benefit greatly from History API support (and is
probably its main use case).
was:
I wonder if Wicket 6/7 has or planned for good history API support, i.e.
navigable ajax updates a la Twitter/Facebook?
If not then I'd like to propose... It'd make Wicket not only very relevant but
a breakthrough in a *post*-HTML5 world.
Originally posted at
https://issues.apache.org/jira/browse/WICKET-3813?focusedCommentId=13720564&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13720564
> History API support for navigable AJAX pages/components
> -------------------------------------------------------
>
> Key: WICKET-5290
> URL: https://issues.apache.org/jira/browse/WICKET-5290
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 7.0.0
> Reporter: Hendy Irawan
>
> I wonder if Wicket 6/7 has or planned for good history API support, i.e.
> navigable ajax updates a la Twitter/Facebook?
> If not then I'd like to propose... It'd make Wicket not only very relevant
> but a breakthrough in a *post*-HTML5 world.
> Originally posted at
> https://issues.apache.org/jira/browse/WICKET-3813?focusedCommentId=13720564&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13720564
> [~mgrigorov] responded:
> > Do you know of a good JS History library ?
> > All I have tried have issues for different browsers.
> What I ever used is Backbone. Which is a great all around library.
> Snippet from http://backbonejs.org/#Router :
> <blockquote>
> Web applications often provide linkable, bookmarkable, shareable URLs for
> important locations in the app. Until recently, hash fragments (#page) were
> used to provide these permalinks, but with the arrival of the History API,
> it's now possible to use standard URLs (/page). Backbone.Router provides
> methods for routing client-side pages, and connecting them to actions and
> events. For browsers which don't yet support the History API, the Router
> handles graceful fallback and transparent translation to the fragment version
> of the URL.
> </blockquote>
> Breadcrumb components would benefit greatly from History API support (and is
> probably its main use case).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
