On Mon, Dec 21, 2009 at 11:11 AM, Dmitriy Igrishin <[email protected]> wrote: > Hello Wim, > Thank you very much! We configured Tomcat as advised us Koen. Works well > now. However, there is a problem with Safari (tested on Safari 4.0.4). When > the user leaves the application and goes to another site (enters another > address in the address bar of the browser) and then comes back using the > back button, the application ceases to respond to a click on any > WAnchor anchor. However, the application continues to correctly respond to > clicks on WPushButton's, for example. The problem on the client side, > because the data is absolutely not sent to the server when user click on > WAnchor's.
For note, I experience this *exact* same thing using Google Chrome (both chrom and safari use webkit as the back-end of course). I thought it was a configuration mess-up I did or an artifact of how the system works, but yes, I do confirm that happens. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
