Details
Bug
Critical
Description
noted in the forum: http://www.icefaces.org/JForum/posts/list/0/3431.page#16051
You have to use a <redirect/> in a navigation-rule to get ICEfaces to set the
new viewID in the browser's url. This breaks the back and forward buttons and is
unexpected behaviour. Is it possible to reset the browser history without a
redirect, as it's done in the this.connection.onRedirect() function
(application.js)? like with window.location.replace(url)
You have to use a <redirect/> in a navigation-rule to get ICEfaces to set the
new viewID in the browser's url. This breaks the back and forward buttons and is
unexpected behaviour. Is it possible to reset the browser history without a
redirect, as it's done in the this.connection.onRedirect() function
(application.js)? like with window.location.replace(url)
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
I need a test case to understand what the real problem is.
Show
Mircea Toma
added a comment - I need a test case to understand what the real problem is.
invalid, only redirects should change the browser url
Show
Philip Breau
added a comment - invalid, only redirects should change the browser url
Mircea, would it be simple to package a URL that would resolve to the current view with any update and
change the URL? Note that this should be an optional feature as some applications would prefer to
maintain a constant entry URL even though they are moving through different states internally.