#31493 [Opn->Fbk]: navigating to javascript:anything kills IE

ID: 31493 Updated by: wez@php.net Reported By: csaba at alum dot mit dot edu -Status: Open +Status: Feedback Bug Type: COM related Operating System: Win XP Pro PHP Version: 5.0.3 New Comment: You should never call sleep() in a script that uses COM, as deadlocks and bad mojo can result. Instead, use com_message_pump() and specify your delay in milliseconds. If that doesn't help any, I'll try to look into this problem later in the week. Previous Comments: ------------------------------------------------------------------------ [2005-01-17 04:02:24] csaba at alum dot mit dot edu As a double check, I downloaded, then installed, PHP ver 5.0.4-dev (cli) (built Jan 17 2005 02:30:00). Still the same problem. IE goes away (and rings a bell) as soon as the Navigate is hit. ------------------------------------------------------------------------ [2005-01-15 17:35:38] derick@php.net You ofcourse need to reboot AFTER you installed it... ------------------------------------------------------------------------ [2005-01-14 10:33:59] csaba at alum dot mit dot edu Fair enough. I have just now rebooted, then downloaded and installed PHP ver 5.0.4-dev (cli) (built Jan 14 2005 02:20:54). Still the same problem. IE goes away (and rings a bell) as soon as the Navigate is hit. ------------------------------------------------------------------------ [2005-01-14 09:09:56] derick@php.net Reboot... windows sometimes caches DLLs. ------------------------------------------------------------------------ [2005-01-14 00:19:52] csaba at alum dot mit dot edu Thanks for looking into this. I downloaded and just now tested with the 13 Jan 04 PHP version 5.0.4.dev and regretably the problem is still there (though I replaced all the files, I did not reboot my PC, however). To ensure it's not a quoting situation, I also tested with: $nav = "javascript:alert(7);"; Csaba ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/31493 -- Edit this bug report at http://bugs.php.net/?id=31493&edit=1