Its not the tag itself (tags are server side and just output html to the
response stream in the end) that has anything to do with this, but rather
the browser.

AFAIK - browsers will submit in the order they are on the page(*see note
below). I dont know if this is in the html spec or not (I suggest you look
it up to check!), but think a lot of sites would break if it werent the
case!

btw: dont forget that NOTHING is submitted for an unticked checkbox.
If your page is:
[x] foo (value=a)
[x] bar (value=b)
[ ] baz (value=c)
[x] bob (value=d)
you will get back the array of submitted values:
a,b,d
-Which means that if they all submit the same value you will not actually
have any idea which ones were actually picked! - So you still need to give
each a different submit value anyhow!

(*)If you move the checkboxes around the page with javascript DOM
manipulation however, for example reordering their nodes in the DOM you
could run into problems. IE submits in the order they appear in the DOM at
submit time, but Netscape6 seems to submit in the order they first appeared
(perhaps using the elements array and not the dom node tree to manage it?).
I had this problem in a special reorderable table widget Id implemented, and
to make it work in netscape I actually had to parse the dom tree at submit
time and create a concatenated ordered string of submit values to submit
instead of relying on the submitted checkboxes themselves!

-----Original Message-----
From: Weibert, Jason (NBC) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 23 January 2003 12:32
To: '[EMAIL PROTECTED]'
Subject: html multibox tag-- order of checked items in array


Does the html multibox tag guarantee that the array of "checked" items will
be populated in the same order that they occur in on the JSP page (i.e. top
to bottom) after a submit?  I need to make sure that the value from the
first checkbox selected is in the zero position of the array and so on...


        Because e-mail can be altered electronically,
        the integrity of this communication cannot be guaranteed.

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to