I see this on recent builds and it blocks my dogfood use of mozilla. 1) From a browser window, choose File | Open Location 2) From the open location dialog, click the browse button and pick a file 3) Pick "new Composer window" from the pop up menu 4) click the open button (may need to edit file name to get button enabled) Notice that a Composer window opens: it has no closebox, it doesn't open the local page, it loads a search page. Please fix ASAP!

fyi, we just checked this out and no one on Browser blackbox sees this on MacOS 8.6 or 9 or WinNT or Win98 or RH Linux 6 with the 2000032306 beta bits.

brade, no on in QA can reproduce this on commercial branch bits today, all platforms. We would like to mark works for me. Did you use ftp://sweetlou/products/client/seamonkey/macos/8.x/ppc/2000-03-23-05-M15-nb1b/ OR ftp://sweetlou/products/client/seamonkey/macos/8.x/ppc/2000-03-23-08-M15/ Netscape or Mozilla bits?

This works fine for me too with the Windows beta at least. Can someone try this on a trunk build?

This is not a beta1 branch bug report; this is a trunk bug report. I see this with a Netscape build (non-installer) on Macintosh.

I see this on the trunk too. The composer window opens, I get a dialog that reads "www.chrome,all,dialog%3dno.com could not be found, and the composer window doesn't load anything.

Loading a local file via the Open Location dialog looks messed up in both Composer and Browser. It looks like Ben was the last person to mess with this code.

CVS blame shows that danm added the delayedOpenWindow code to navigator.js, so I'm assigning this to him. General comment: All the "open location" code should be in global files, not browser! Also, all this worked in the code just before Beta1 -- let's have some better testing!

And perhaps better searching for existing bug reports. Another dup of 30014. *** This bug has been marked as a duplicate of 30014 ***

try again

Doh! We need to learn to do a better job placing our fingers on the keyboard, too! That's 33114 that's a dup of this one (I'm resolving this as a dup of that since I've reported the fix there already). *** This bug has been marked as a duplicate of 33114 ***

verified