Using 3/16 build on Win 95, Win NT, Win 98, Mac8.5 and Linux. Open URL. No need to complete the form. Click 'Submit Order'. Expected result: Form should be sent immediately. Actual result: Form submission is delayed by the following prompted questions appearing in the console: 1. Do you want to put the values on this form into your wallet? 2. For your convenience, the browser can remember your user names and passwords so that you won't have to re-type them when you return to a site. Your passwords will be obscured before being saved on your hard drive. Do you want this feature enabled? After these questions are answered, the form is submitted. Win 95, Win 98, Win NT: Bug Linux, Mac8.5: OK

This may be the expected behavior. Reassigning to Steve to verify.

I believe that this is indeed the expected behavior. This should be marked as invalid - I'll leave that to Steve.

how could that be the expected behavior in an optiomized build? The user is not going to have a command window open when they run Navigator, and what the heck does the wallet have to do with submitting a form with an email address as the submit value?

Yes, this is the expected behavior. The use of the console window is necessary because our product still doesn't have the infastructure in place to support dialog windows. So not only form submission, but any other time a dialog window is supposed to pop up, the console window is being used instead. Try setting your cookie preference to warn-before-accepting-a-cookie and see where that warning occurs. But, due to an overwhelming outcry, I have temporarily put these messages under control of a perference and that preference is off by default. That preference will not be present in the final release and the messages will once again always appear. See bug report 3845 and 3849 for details. *** This bug has been marked as a duplicate of 3845 ***

actually it isn't expected behavior as you stated in your note, the expected behavior is a dialog box, not command line entries -- that was the point of my comment. I did not know that the backend to the wallet was complete, which is a total surprise. Since the wallet infrastructure is now presumed to be complete and functional, then yes it does make sense to have a notification. However, if wallet isn't complete, then this should not be turned on.

Aside from the issue of whether or not the behavior is correct, the behavior is not consistent across platform. Is this a different problem?

Wallet and Single signon have not been turned on yet for mac or unix. That explains why the behavior is not consistent across platforms.