createPopup anomaly after XP SP2

[Gene Black]

We have a menuing system which creates hierarchical menus by using
createpopup from a window which was created using createpopup. With XP SP2
it
seems that the second popup gets Z-ordered underneath the previous window.

This apparently is being cause when IE checks the window restrictions on the
popup. It appears that this is done last-first (newest to oldest) leaving
the oldest popup in the top z-order. (this is only a guess). If the window
restrictions were set going from first-last (oldest to newest) it might
rectify this problem. Unfortunately these is no access to the z-order
attribute on a popup created with createPopup, the default behaviour has
always been that the most recently created would be on top.

This behavior can be rectified by turning off the setting in

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet
Explorer\Main\FeatureControl\FEATURE_WINDOW_RESTRICTIONS

But the problem then is that the window size restrictions (as exposed
through the DHTML screen object screen.width, screen.height,
screen.availWidth, screen.availHeight) do not return the same values as in
previous versions of IE 6. Does anyone know of a way to rectify this?

The simplest solution would include a way for the createpopup to correctly
display the most recently shown popup on top of the window from which is was
created.

This should be able to be done without changing registry settings.

 

[Robert Aldwinckle]

We have a menuing system which creates hierarchical menus by using
createpopup from a window which was created using createpopup. With XP SP2
it
seems that the second popup gets Z-ordered underneath the previous window.

Are you using About:Blank as the default target for the open function?
If so, you may be seeing something related to a silliness that I frequently
see (for example on Windows Update, MSDN, etc.) because I happen to
have About:Blank in my Local Intranet sites: I get a warning prompt
about a cross-zone transfer but it doesn't matter what I reply to it, OK
or Cancel; whatever the script needs it for is done regardless.


---

 

[Gene Black]

Nope, that's not the issue. That issue is already addressed in the code.
(about:blank is a different security zone than an internet page).

This code works great in IE 6 prior to XPSP2