Return-Path: Delivered-To: apmail-jakarta-struts-user-archive@apache.org Received: (qmail 91122 invoked from network); 9 Sep 2002 09:44:16 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 9 Sep 2002 09:44:16 -0000 Received: (qmail 7880 invoked by uid 97); 9 Sep 2002 09:44:44 -0000 Delivered-To: qmlist-jakarta-archive-struts-user@jakarta.apache.org Received: (qmail 7863 invoked by uid 97); 9 Sep 2002 09:44:43 -0000 Mailing-List: contact struts-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list struts-user@jakarta.apache.org Received: (qmail 7851 invoked by uid 98); 9 Sep 2002 09:44:43 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Reply-To: From: "Andrew Hill" To: "Struts Users Mailing List" Subject: RE: [OT] JavaScript auto-submit form Date: Mon, 9 Sep 2002 17:45:33 +0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hmm. Seems a correction is in order. It seems that if other javascripts on the page have compilation problems, this can stop NS6 invoking its onload behaviour (while it would seem that IE and Mozilla are not so badly affected). Thanks to Arron Bates for pointing this out to me. :-) Reducing my test form to a much simpler case made it work, so must have been some other problem among all the other garbage in the page (yep. I was trying to save time by tacking my experiments onto an existing page which Id been using to experiment with other things!) as the following works fine in NS6: -----Original Message----- From: Andrew Hill [mailto:andrew.david.hill@gridnode.com] Sent: Monday, September 09, 2002 14:40 To: Struts Users Mailing List Subject: RE: [OT] JavaScript auto-submit form Been trying to duplicate your results. I was experimenting with using (body tag) onload="document.forms['formname'].submit();" to submit the form as soon as it had loaded (this can be a useful way of posting parameters to other applications). This worked in Mozilla, and IE5. It didnt work in Netscape 6 (esentially an earlier version of Mozzila). Furthermore, changing to onload="alert('hello');" worked in IE5 and Mozilla, but again failed in Netscape 6. It rather looks like NS6 doesnt support the onload attribute for the body tag! Can this be true - perhaps its a bug in the NS version of Mozilla that was fixed later? I _was_ however able to submit the form from a script block after the form in all three browsers. What exactly was the nature of the problem trying to submit from a script block in mozilla? -----Original Message----- From: wbchmura@Ensign-BickfordInd.com [mailto:wbchmura@Ensign-BickfordInd.com] Sent: Saturday, September 07, 2002 01:41 To: struts-user@jakarta.apache.org Subject: RE: [OT] JavaScript auto-submit form here is a snippet from one of my pages... You only need the submit line. Works in mozilla (I use it)

Now, I am gonna go find Mark and some beers... -----Original Message----- From: cbartl03 [mailto:cbartl03@sprintspectrum.com] Sent: Thursday, September 05, 2002 4:24 PM To: struts-user Subject: RE: [OT] JavaScript auto-submit form What do you mean by "auto-submit"? When should the form be automatically submitted? On page load? When the user has filled out all the fields? > -----Original Message----- > From: Eddie Bush [mailto:ekbush@swbell.net] > Sent: Thursday, September 05, 2002 3:13 PM > To: Struts Users List > Subject: [OT] JavaScript auto-submit form > > > Could any of you suggest a way for me to get Netscape/Mozilla to > auto-submit a form via JavaScript? I have two ways that work > just fine > under IE and Opera ... but, ... suffice it to say I'd like a > cross-browser solution :-) > > Things I have tried: > * A JavaScript