Derrell, I agree that we should embrace this security measure - it protects us from the "other" developers.
However, this touches on another post some months ago, where the IE security bar blocked an action and then reloaded the entire page when the user verified the action. In a normal webpage scenario, this is just fine, but in an RIA environment, this is disastrous. I wonder if the framework could provide a "check" function at load time to allow a user to "verify" actions for the site prior to loading and initiating the app, in order to avoid a later incident that reloads the entire RIA page. An app developer would include this function at startup to initiate an arbitrary "trigger" that forces the browser to offer the acceptance option and prevent future dialogs. I don't know what this function would need to execute in order to trigger the acceptance, but others probably have a better knowledge of what it would take. Being able to intercept this situation and address it at app startup would provide a solution for Ken. I know it's possible for the user to configure this setting on a domain-wide basis through the browser settings, but many users don't know how or don't think to do it before loading a Qooxdoo application. Any ideas on a solution? Has this been considered? Maybe there's already an enhancement bug entered in bugzilla for something like this? Gene On Mon, 2009-12-28 at 08:33 -0500, Derrell Lipman wrote: > On Mon, Dec 28, 2009 at 08:27, Ken MacDonald <drken...@gmail.com> > wrote: > > Hi Andreas, > Thanks for the snippet. Unfortunately, IE can tell whether the > event handler was just 'called' or whether it was fired. See > the difference in IE8, making sure that your popup blocker is > enabled: > > > This sounds like a "good thing". There should be NOTHING -- no trick > of any type -- that any arbitrary JavaScript code can do to defeat my > pop-up blocker. If there were, it would be impossible to block pop-ups > because all of those sites that want to create obnoxious pop-ups would > just use that trick. I understand that you may have what you consider > a legitimate reason to try to get around a pop-up blocker, but only > the individual user can select when he's willing to receive a pop-up > and when he's not. > > Derrell > > > > ------------------------------------------------------------------------------ > 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 > _______________________________________________ qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------ 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
_______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
