Our page designer wants our newest app to open new tabs for each detail record opened off a list. Within that tab would be potentially multiple pages in varying orders related to that record, and then the user might close it or leave it open, return to the list and move around a few times (ajax and page loads) before opening other details records and so on...
We've always been a one tab operation with Wicket. It's pretty stateful, and I told our designer that I was worried give this statefulness how Wicket would react to that design. Am I being overly cautious? How will Wicket handle this possible random moving about. When one moves from one tab to another and therefore to pages whose states are different, how does Wicket handle that? Do I need to design my pages differently or take any special action? -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
