Re: [OLmws] Popup blocker for IE in XP SP2
- ----- Original Message -----From: Dennis SandowSent: Thursday, September 02, 2004 5:41 PMSubject: Re: [OLmws] Re: Crossframe and XP SP2With regard to your last question, seehttp://msdn.microsoft.com/security/productinfo/xpsp2/default.aspx?pull=/library/en-us/dnwxp/html/xpsp2web.asp#xpsp_topic2
where they define "popups"
What does Internet Explorer consider a pop-up window?
Internet Explorer will attempt to block any window opened automatically from script, with the exception of createPopup(). Some common functions that are affected are window.open(), showModelessDialog(), showModalDialog(), and showHelp(). (Note: Targeting the search pane automatically is also blocked due to pop-up blocking restrictions.)
A pop-up window opened as a direct result of a user action (e.g., clicking a page element) will not be blocked. Pop-up blocking does not apply by default to the Intranet or Trusted Sites Zones.
How can I tell if Internet Explorer has blocked my pop-up window?
Functions that return a window object will return null if the window is blocked. Always check the return value of window.open() before using it to avoid script errors when pop-ups are blocked.Apparently, if window.open() comes from an <a href= > or onclick= , then that user activity implicitly overrides blocking.
And apparently, if you declare the domain to be a "trusted site" (or intranet/local) , then that explicitly overrides blocking of hard-coded popups..
If the site is not "trusted", then auto-popups are blocked. (ex - most sponsored sites.)Dennis,That reads in an encouraging way for DHTML popups, but also read this:Q: What does Internet Explorer consider a pop-up window?Internet Explorer will attempt to block any window opened automatically from:
I hope that third item concerns the window.open() types of popups invoked via the content of a DHTML (positioned div) popup, and that the DHTML popup itself is excluded from the "pop-up window" block along with the window.createPopup() type. But I still would like empirical confirmation from someone who has installed XP SP2. Even if potentially included in the block, presumably DHTML popups invoked via the onmouseover, onclick or onmousemove events would be excluded by virtue of being "a direct result of a user action" but what about onload invocations, or invocations via a shell (wrapper) script?Fote--
- a script, with the exception of createPopup()
- modal and modeless dialogs
- DHTML elements overlapping content on the page.