2 errors

[Paul Kafasis]

Boo, no new SPs on Saturdays/Sundays? :) Oh well, we'll survive. 

www.launch.com - This site turns up in some funky, weird characters. I've
posted a screenshot on my web server, at http://pxr.dyndns.org/images/
launch.jpg

That screenshot also shows a second error that I come across, where the
toolbar goes blank. Closing the fixes it. Clicking one of my favorites
links fixes it. However, very ugly and annoying. 

The real pisser was I only needed to load launch.com to get off their
freakin' mailing list.

Keep up the good work!

-Paul

>So, Ken walked up to me this evening, and he said something that made my 
>blood run cold, but which I think is a really good idea, so I gulped and 
>said "Let's do it."
>
>This is the situation; we want to release OmniWeb 4.1 at Macworld SF. 
>This gives us some time to work with, but not huge gobs of it. To make 
>the most of the time we do have, we plan to do the following:
>
>-Ken shall lock himself in his office for the next week, fixing bugs 
>like there's no tomorrow.
>-Everyone here shall leave him alone for that period, unless they're 
>helping him fix bugs.
>-We're going to release a sneakypeek each day until Dec. 14, at which 
>time we're essentially going to freeze the app and put it out for a 
>public beta.
>
>Once we go public beta, the changes we make to the code will be much 
>smaller than they were in the sneakypeeks. No new features, no UI 
>changes, no additional JavaScript fixes. (As as aside; we didn't get as 
>much compatibility work done as we originally intended to put into 4.1; 
>things took longer than we expected, and we just plain ran out of time. 
>For this, we apologize.)
>
>Things we're trying to fix between now and next Friday:
>- Find a way to work around Apple mis-positioning Java Applets in our 
>windows.
>- Not always ensuring that line termination in forms has been converted 
>to CR/LF before submission.
>- Keyboard input to a Netscape plug-in not supported (So, you can't fill 
>out flash forms, for example)
>- Netscape plugins cannot be displayed outside of an HTML page. (So, 
>linking directly to a flash file will download it and open the file in 
>QuickTime Player.)
>- There are still some window-closing crashers, mostly associated with 
>editing source code.
>- We're adding the "if you're a registered user, you send tech support 
>email that gets higher priority" feature to the help menu.
>- Restore auto-open functionality for downloads that are handed off to 
>certain apps.
>      -Disk Copy
>      -Stuffit Expander
>      -Preview.app
>      -QuickTime Player
>      -Text Edit
>      -[Some other built-in apps. Suggestions? This will be something 
>that power users can change in their defaults, so we're mostly thinking 
>about things that should be turned on for average users.]
>- Slow printing. (No promises here, but we're making a last-ditch 
>attempt.)
>- Better handle pages that use "about://" to open new windows.
>- Fold in support for "telnet://" URLs. (Code's already written, we just 
>need to fold it in and test it)
>- Problems with links using named anchors.
>- Find seems to have stopped dealing very well with frames in one of the 
>earlier sneakypeeks.
>
>Now, if something you cannot live without having fixed is not on that 
>list, we want you to let us know.  Essentially, this is the point in the 
>wedding where you "speak now, or hold your peace (at least till version 
>5)", and the part where we promise to listen extra carefully and do our 
>level best to make sure that it happens.
>
>Please understand that we're going to be working like madmen between now 
>and then, so bugs of the "Page X doesn't work, but it works in IE" 
>variety are not going to have much of a chance in the next week. If it's 
>something that you know we're doing incorrectly, or something that we 
>used to do correctly but broke somewhere along the way, that's more 
>likely to get fixed. We have to spend the next week fully in "fixing 
>what's broken" mode, as opposed to "adding support for something that we 
>cannot do at all in this version". If it's a problem that you know the 
>solution to, can provide a test case, and can quote the previous version 
>of OmniWeb that it used to work in to us bible, chapter, and verse, you 
>stand an even better shot.
>
>So send in those bug reports to sneakypeek at omnigroup.com. Download those 
>daily builds in the sneakypeek directory, and be sure to let us know 
>what you're seeing and what you need. It's going to be a crazy couple of 
>days, but we could end up with a much better OmniWeb at the end of the 
>process.
>
>We still plan to implement everything that you've submitted in the past, 
>and everything we've committed to implement in the future, but we know 
>that there may be some things that we've overlooked or forgotten about. 
>Let us know where we broke something, let us know what we're doing 
>incorrectly; we promise to listen really closely while you do, and to do 
>everything we can to get it implemented by the freeze so you can have it 
>in OmniWeb 4.1.
>
>As always, everyone, we really appreciate your patience and your 
>assistance. You've all been delivering the highest level of quality 
>feedback that I've seen, and you've been doing it consistently as long 
>as I've been reading your mail. We literally cannot make OmniWeb happen 
>without your help, and I just want to take the opportunity to deliver a 
>thank you to everyone on this list.
>
>Sincerely,
>
>Brian Covey
>Support Engineer
>Omni Group
>
>_______________________________________________
>OmniWeb-l mailing list
>OmniWeb-l at omnigroup.com
>http://www.omnigroup.com/mailman/listinfo/omniweb-l