Issue 2472: Indirect call to window.open, i.e. through flash, results in a blocked popup http://code.google.com/p/chromium/issues/detail?id=2472
Comment #10 by [EMAIL PROTECTED]: Ananta mentioned to me that the problem here is that the popup is opened from a timer that is initiated on a user-action. The timer fires after the user-action has completed, so we don't consider it user-initiated. Ananta, please correct me if that is wrong. If that is the case, it seems to me that the ideal solution would be that the function executed in the timer could also open popups. Although, I can see this being abused. Seems like we should have some limit like saying that only one popup can be opened from a timer that was initiated from a user-action. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to chromium-bugs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
