When opening a new window in IE6 on WinXP Pro, whether
by using "Open link in new window" or when done internally
via target= or Javascript, the new window's frame will come
up, and then freeze there indefinitely with no content.

It's quasi-transparent, meaning I can see what's behind
it, but if I drag it, it takes that snapshot of the
background with it.

If I click the Close button, it closes without fuss. If
I'm given the toolbar, I can click Stop, and it will then
fill in the URL and I can click Go or Reload and the
window WILL load normally. Unfortunately, that doesn't
work when Javascript opens a new toolbar-less window.


--
"The universe runs on the complex interweaving of three
elements: energy, matter, and enlightened self-interest."
- G'Kar

Your friend and mine,
Matt Ion
Molten Image Media

Matt,
See:
http://www.fjsmjs.com/OE/nolinks.htm
http://support.microsoft.com/?kbid=281679
http://www.mvps.org/inetexplorer/ans...htm#hyperlinks
http://www.mvps.org/inetexplorer/answers.htm#new_window

Regards,
Don
--
MVP IE/OE
Please reply to the newsgroup so that others may participate.

"Matt Ion" <soundy[at]moltenimage.com> wrote in message
news:(E-Mail Removed)...
> When opening a new window in IE6 on WinXP Pro, whether
> by using "Open link in new window" or when done internally
> via target= or Javascript, the new window's frame will come
> up, and then freeze there indefinitely with no content.
>
> It's quasi-transparent, meaning I can see what's behind
> it, but if I drag it, it takes that snapshot of the
> background with it.
>
> If I click the Close button, it closes without fuss. If
> I'm given the toolbar, I can click Stop, and it will then
> fill in the URL and I can click Go or Reload and the
> window WILL load normally. Unfortunately, that doesn't
> work when Javascript opens a new toolbar-less window.

There we go, something in there did the trick. Had to reboot for it to take
effect, but it seems to be good now. I think the one thing that did it was
one of the HKEY_CLASSES_ROOT reg keys mentioned in the Microsoft document:
of the three, the first one pointed at some different DLL rather than
URLMON.DLL.

Restoring that key didn't fix it immediately so I went through all the other
steps, including re-registering all the listed DLLs, and all the other
listed keys seemed to be intact, but as I say, none of the steps helped
until after a reboot, so I can't say for sure which one really did the job.
But, something did, and all is good now

Thanks, Don!

"Don Varnau" <don_04[at]varnau[dot]org> wrote in message
news:(E-Mail Removed)...
> Matt,
> See:
> http://www.fjsmjs.com/OE/nolinks.htm
> http://support.microsoft.com/?kbid=281679
> http://www.mvps.org/inetexplorer/ans...htm#hyperlinks
> http://www.mvps.org/inetexplorer/answers.htm#new_window
>
> Regards,
> Don
> --
> MVP IE/OE
> Please reply to the newsgroup so that others may participate.
>
> "Matt Ion" <soundy[at]moltenimage.com> wrote in message
> news:(E-Mail Removed)...
> > When opening a new window in IE6 on WinXP Pro, whether
> > by using "Open link in new window" or when done internally
> > via target= or Javascript, the new window's frame will come
> > up, and then freeze there indefinitely with no content.
> >
> > It's quasi-transparent, meaning I can see what's behind
> > it, but if I drag it, it takes that snapshot of the
> > background with it.
> >
> > If I click the Close button, it closes without fuss. If
> > I'm given the toolbar, I can click Stop, and it will then
> > fill in the URL and I can click Go or Reload and the
> > window WILL load normally. Unfortunately, that doesn't
> > work when Javascript opens a new toolbar-less window.
>

You're welcome.
Don

"Matt Ion" <soundy[at]moltenimage.com> wrote in message
news:(E-Mail Removed)...
> There we go, something in there did the trick. Had to reboot for it to
take
> effect, but it seems to be good now. I think the one thing that did it
was
> one of the HKEY_CLASSES_ROOT reg keys mentioned in the Microsoft document:
> of the three, the first one pointed at some different DLL rather than
> URLMON.DLL.
>
> Restoring that key didn't fix it immediately so I went through all the
other
> steps, including re-registering all the listed DLLs, and all the other
> listed keys seemed to be intact, but as I say, none of the steps helped
> until after a reboot, so I can't say for sure which one really did the
job.
> But, something did, and all is good now
>
> Thanks, Don!