Re: chrome + wicket ajax + back button = problem?
I have (I am using MixedParamHybridUrlCodingStrategy) however in this case the browser is not contacting the server on back button click so the UrlCodingStrategy does not come into play. Ryan On Wed, Oct 6, 2010 at 4:13 PM, mzem...@osc.state.ny.us wrote: I've had similar issues, have you tried HybridUrlCodingStrategy? Notice: This communication, including any attachments, is intended solely for the use of the individual or entity to which it is addressed. This communication may contain information that is protected from disclosure under State and/or Federal law. Please notify the sender immediately if you have received this communication in error and delete this email from your system. If you are not the intended recipient, you are requested not to disclose, copy, distribute or take any action in reliance on the contents of this information.
Re: chrome + wicket ajax + back button = problem?
See https://issues.apache.org/jira/browse/WICKET-923 for a solution. On Mon, 11 Oct 2010 09:31 -0500, Ryan Crumley crum...@gmail.com wrote: I have (I am using MixedParamHybridUrlCodingStrategy) however in this case the browser is not contacting the server on back button click so the UrlCodingStrategy does not come into play. Ryan On Wed, Oct 6, 2010 at 4:13 PM, mzem...@osc.state.ny.us wrote: I've had similar issues, have you tried HybridUrlCodingStrategy? Notice: This communication, including any attachments, is intended solely for the use of the individual or entity to which it is addressed. This communication may contain information that is protected from disclosure under State and/or Federal law. Please notify the sender immediately if you have received this communication in error and delete this email from your system. If you are not the intended recipient, you are requested not to disclose, copy, distribute or take any action in reliance on the contents of this information. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: chrome + wicket ajax + back button = problem?
I've had similar issues, have you tried HybridUrlCodingStrategy? Notice: This communication, including any attachments, is intended solely for the use of the individual or entity to which it is addressed. This communication may contain information that is protected from disclosure under State and/or Federal law. Please notify the sender immediately if you have received this communication in error and delete this email from your system. If you are not the intended recipient, you are requested not to disclose, copy, distribute or take any action in reliance on the contents of this information.
Re: chrome + wicket ajax + back button = problem?
What is interesting is this is not a wicket specific issue however it is more serious when using wicket than other frameworks due to the expired links causing errors when they reappear. I created a very simple version of the problem. Chrome and IE8 exhibits the problem but Firefox and Safari do not: http://www.cupofcrumley.com/chrome-test/Page1.html http://www.cupofcrumley.com/chrome-test/Page1.htmlRyan On Fri, Sep 24, 2010 at 1:48 AM, Peter Karich peat...@yahoo.de wrote: I had the same problem ... Take a look at http://www.richardnichols.net/2010/03/apache-wicket-force-page-reload-to-fix-ajax-back/ isn't there a better fix? E.g. it seems to me that this 'hack' avoids client-side js caching (or is this a wrong observation)? Regards, Peter. -- http://jetwick.com twitter search prototype - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: chrome + wicket ajax + back button = problem?
Yes, it is not repeatable on FF because FF does page caching which IE does not for Back history. Your page must be stateless on the server side. Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Sun, Oct 3, 2010 at 3:47 PM, Ryan Crumley crum...@gmail.com wrote: What is interesting is this is not a wicket specific issue however it is more serious when using wicket than other frameworks due to the expired links causing errors when they reappear. I created a very simple version of the problem. Chrome and IE8 exhibits the problem but Firefox and Safari do not: http://www.cupofcrumley.com/chrome-test/Page1.html http://www.cupofcrumley.com/chrome-test/Page1.htmlRyan On Fri, Sep 24, 2010 at 1:48 AM, Peter Karich peat...@yahoo.de wrote: I had the same problem ... Take a look at http://www.richardnichols.net/2010/03/apache-wicket-force-page-reload-to-fix-ajax-back/ isn't there a better fix? E.g. it seems to me that this 'hack' avoids client-side js caching (or is this a wrong observation)? Regards, Peter. -- http://jetwick.com twitter search prototype - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: chrome + wicket ajax + back button = problem?
Just to clarify: The page in the example link I sent is stateless (it's static html). The other point is that Chrome and IE do not fetch the original page on back button click. They are serving the original html straight from the cache (without the DOM modifications). It sounds like the only fix is to update the page headers so that no browser will ever cache the page. That seems like an overkill but so far I haven't found any other solution that works across browsers. This seems like a very common scenario... is it also very common to set all the no-cache headers? Ryan On Sun, Oct 3, 2010 at 5:56 PM, Zilvinas Vilutis cika...@gmail.com wrote: Yes, it is not repeatable on FF because FF does page caching which IE does not for Back history. Your page must be stateless on the server side. Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Sun, Oct 3, 2010 at 3:47 PM, Ryan Crumley crum...@gmail.com wrote: What is interesting is this is not a wicket specific issue however it is more serious when using wicket than other frameworks due to the expired links causing errors when they reappear. I created a very simple version of the problem. Chrome and IE8 exhibits the problem but Firefox and Safari do not: http://www.cupofcrumley.com/chrome-test/Page1.html http://www.cupofcrumley.com/chrome-test/Page1.htmlRyan On Fri, Sep 24, 2010 at 1:48 AM, Peter Karich peat...@yahoo.de wrote: I had the same problem ... Take a look at http://www.richardnichols.net/2010/03/apache-wicket-force-page-reload-to-fix-ajax-back/ isn't there a better fix? E.g. it seems to me that this 'hack' avoids client-side js caching (or is this a wrong observation)? Regards, Peter. -- http://jetwick.com twitter search prototype - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: chrome + wicket ajax + back button = problem?
I had the same problem ... Take a look at http://www.richardnichols.net/2010/03/apache-wicket-force-page-reload-to-fix-ajax-back/ isn't there a better fix? E.g. it seems to me that this 'hack' avoids client-side js caching (or is this a wrong observation)? Regards, Peter. -- http://jetwick.com twitter search prototype - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: chrome + wicket ajax + back button = problem?
Take a look at http://www.richardnichols.net/2010/03/apache-wicket-force-page-reload-to-fix-ajax-back/ On Wed, Sep 22, 2010 at 12:58 PM, Ryan Crumley crum...@gmail.com wrote: All, I ran into strange behavior involving wicket ajax updates + chrome + back button. I am pretty sure the issue is not caused by wicket but I am hoping the problem might sound familiar to someone and they can point me in the right direction. The scenario goes like this: - An ajax request is made that updates the DOM. - The user navigates to another page by clicking on a link. - The user uses the browser back button to go back to the original page. After clicking back Google Chrome shows the page as it was originally rendered (before the DOM update). All other browsers show the page as it was when the user left the page (with the DOM update). Besides the possibility of showing stale data the other problem is that the page state has been altered by the ajax request and links that were originally rendered may no longer be valid. I found a few links where people are having similar issues: http://www.maintaino.com/nuts-and-bolts/2010/04/08/teaching-chrome-not-to-cache-your-rails-pages/ Possibly related to using jQuery and/or window.onUnload() and bfcache: http://stackoverflow.com/questions/158319/cross-browser-onload-event-and-the-back-button https://developer.mozilla.org/En/Using_Firefox_1.5_caching In addition to using Wicket 1.4.12 I am also using jQuery 1.4.2 and google analytics on these pages. I don't think any unload handlers have been added however my only check was looking at all the attributes on the window object via the inspector. Has anyone else seen similar behavior? Even better, anyone else have a solution? You may be seeing errors like this one in your logs: org.apache.wicket.protocol.http.request.InvalidUrlException: org.apache.wicket.WicketRuntimeException: component wid1:wid2:1:wid3 not found on page com.foo.xxx Thanks! Ryan -- Richard Nichols http://www.richardnichols.net/ :: http://onmydoorstep.com.au/
chrome + wicket ajax + back button = problem?
All, I ran into strange behavior involving wicket ajax updates + chrome + back button. I am pretty sure the issue is not caused by wicket but I am hoping the problem might sound familiar to someone and they can point me in the right direction. The scenario goes like this: - An ajax request is made that updates the DOM. - The user navigates to another page by clicking on a link. - The user uses the browser back button to go back to the original page. After clicking back Google Chrome shows the page as it was originally rendered (before the DOM update). All other browsers show the page as it was when the user left the page (with the DOM update). Besides the possibility of showing stale data the other problem is that the page state has been altered by the ajax request and links that were originally rendered may no longer be valid. I found a few links where people are having similar issues: http://www.maintaino.com/nuts-and-bolts/2010/04/08/teaching-chrome-not-to-cache-your-rails-pages/ Possibly related to using jQuery and/or window.onUnload() and bfcache: http://stackoverflow.com/questions/158319/cross-browser-onload-event-and-the-back-button https://developer.mozilla.org/En/Using_Firefox_1.5_caching In addition to using Wicket 1.4.12 I am also using jQuery 1.4.2 and google analytics on these pages. I don't think any unload handlers have been added however my only check was looking at all the attributes on the window object via the inspector. Has anyone else seen similar behavior? Even better, anyone else have a solution? You may be seeing errors like this one in your logs: org.apache.wicket.protocol.http.request.InvalidUrlException: org.apache.wicket.WicketRuntimeException: component wid1:wid2:1:wid3 not found on page com.foo.xxx Thanks! Ryan
