🚀 go-pugleaf

"Martin C" <martinc@aol.com> wrote in message
news:3f967065@newsgroups.borland.com...

> Yes remy I used it and when I realized what you were doing I
> removed your DISPID_NEWWINDOW2 code, although the
> problem of (Open in new window) command still exist.

Ok then, now we're getting somewhere.  Please post your actual code as it
currently stands.

> That is not correct...even if you are blocking 100% of pop-up
> screens (and what I mean here by pop-up screens is screens that
> pop-up without the user permission)

The WebBrowser does not differentiate between windows that are popped up via
user input, or windows that are popped up via scripting.  A new window is a
new window regardless.

> there is a code (unfortunatly it is in VC) that can be written to see
> if the newly created windows was created based on user selection
> (in other words the user clicked on a link, picture...etc.) then the
> new window will be created without blocking it, please review
> (http://www.codeproject.com/atl/PopupBlocker2.asp)

You said that you were blocking 100% of the windows.  You never said
anything about performing per-window validation to allow/disallow new
windows.  100% means 100%, not 90% or 99.9999%.  100% means *every* window.
In that regard, I commented that blocking 100% of the windows will do
exactly what you claim to be having a problem with - no windows will appear
at all.  That is expected behavior.  If, on the other hand, you are not
actually blocking every single window, then you need to say so.  And more
importantly, if you are *trying* not to block all windows so that some can
go through normally, but no windows are actually being displayed anyway,
then there is a problem with your code, and again, I would have to aks that
you please post your actual code.


Gambit