Hey Michael, 2008/7/2 Koen Deforche <[EMAIL PROTECTED]>: > Two things we could do, one we "must" and one we "should": > > 1) disable events at the server side that should not work. One of the > features built-in to Wt, is that only "exposed" events or resources > are handled at the server side. This must also be the case when a > modal dialog covers other events. In this way, your application logic > cannot be broken.
This is now in CVS. > 2) try to prevent those events on the client-side. I'm not entirely > sure if there is a fool-proof way to do this, but we'll investigate. Still to be done! Regards, koen ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
