IWebBrowser2::Navigate2 with navOpenInNewWindow being blocked by popup blocker

ohadp

The GoogleBar's popup blocker is blocking my calls to Navigate with the flag navOpenInNewWindow

I'm opening a page due to a user's request, so it's funny that he gets this dialog.

Is this normal behavior with IE7/GoogleBar or is there a way to avoid the blocker

Sheng Jiang

You can use IHTMLWindow2::open and check the returned window. Display an error message like "you have popup blocker installed" when the resulted window is null.

ohadp

So for certain there is no way to overcome the blockers using a different method/technique

I would expect popup blockers to get a chance to block things when popped from JS/HTML, not from actual compiled code that the user chose to install, especially with all the activex security now in place.

G Back

> So for certain there is no way to overcome the blockers using a different method/technique

I too would be interested in an answer to this question. How can an IE BHO open a window that is not blocked by IE's internal popup blocker, or any third-party popup blocker

Related, are Google's and Yahoo's popup blockers intended to defend against the windows other BHOs attempt to open, or are they intended to defend against windows opened by client side JavaScript only

Note that Sheng's suggestion of asking the user to disable popup blocking is not an option, since it cannot be disabled per-site, and asking the user to disable popup blocking entirely would create a bad trade-off where a user would have to forgo all popup blocking in order to use a plugin they installed.

Sheng Jiang

A properly written popup blocker should have a per-site configuration. IE's buildin has a white list in its settings window, where Google ToolBar provides the current website's status on the Popup Blocker button. A popup blocker is useless if it hard code a white list (or black list) and does not make it customizable.

Since it is impossible to know what kind of popup blocker is installed, informing the user the new window is blocked is one way to go. The user should have the right to go elsewhere or add the website to the white list of the popup blocker.

G Back

Sheng Jiang wrote:

A properly written popup blocker should have a per-site configuration. IE's buildin has a white list in its settings window, where Google ToolBar provides the current website's status on the Popup Blocker button. A popup blocker is useless if it hard code a white list (or black list) and does not make it customizable. Since it is impossible to know what kind of popup blocker is installed, informing the user the new window is blocked is one way to go. The user should have the right to go elsewhere or add the website to the white list of the popup blocker.

The user could be using our toolbar to open a new window on *any site or page* they are visiting.

It is not useful to ask the user to unblock on a per-site basis, since the use of the toolbar has nothing to do with the site that's currently displaying.

How can I open a new window (at the user's request) without being blocked by a popup blocker

Spawning a new iexplorer process might be an option - but what is the Microsoft-sanctioned way of doing this