occurred using comm bits 2000.05.03.08 on winNT. not a problem on linux or mac. 1. go to File > Open File. 2. in the [native] Open File dialog, open either a plaintext file or an html file that's local to your machine. result: a new web browser window opens (expected), but it is blank (not expected). expected: should display the text or html content.

Ugh. Is this gonna block the tree from openning today?

repro'd on win98 2000050308 question: anyone know if it's been reported yet that you can't type, say, c:\test.html into the textfield of Open Web Location since it reads it as an unregistered protocol? I couldn't find a report but I'd rather not go to the trouble of filing it if someone's aware of its existence already.

I can't reproduce this problem on my WinNT build today. I was able to reproduce the error by entering a local file path into the Open Web Location dialog, but only if I chose "New navigator" (it worked OK loading into "current navigator"). We should open a separate bug on that. Maybe the "Open File" thing is a problem in release builds only? I'll install the official build on Win98 and see what I can find out there.

I was unable to reproduce this on Win98 with the build downloaded from sweetlou.

I can't get the commercial bits to install from sweetlou so that might be the only version of the code where the problem exists. I'll keep trying.

Putting on [dogfood+] radar.

marking this wfm, using this afternoon's respun bits (comm, on winNT)... if *anyone* sees this still, do reopen. :-)

seems to now be working on 2000050309 win98; verif wfm, again, reopen if necessary