Hey Michael, > Whan WDialog is presented using show(), the underlying page seems to be > disabled, > but only 'seems'! :-) It is not accessible by mouse, but if one goes to > browser's ulr input > window and then proceeds to move focus using TAB, then he *can* access > controls from > underlying window. Now WDialog is described as modal in docs and (at > least in my case) > access to the underlying page can screw up application badly. > > Is there any way to disable it?
Good point! 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. 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. Regads, 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
