Form elements no worky in certain cases
Reported by swsnider (at gmail) | May 1st, 2008 @ 06:36 PM
Basically, when trying to update multiple form elements using evalScripts and AjaxUpdater, the elements without name attributes are not updated correctly (due to the prototype cache (I think)). Either this needs to be documented, or (more probably) this needs to be changed -- it is common for input elements not to have name attributes when exclusively used for AJAX calls.
Comments and changes to this ticket
-
John-David Dalton May 1st, 2008 @ 09:32 PM
- → State changed from “new” to “invalid”
Please provide a code snippet or code example.
Elements should be referenced by their unique ID's and not their names.
-
swsnider (at gmail) May 1st, 2008 @ 10:59 PM
A snippet is in the works (I need to distill the code down to a minimal snippet. My point is that we are not using the names (which is why the elements do not have them). Our problem is that prototype is using the names in some sort of cache array, which is screwing up our code in wierd ways.
-
John-David Dalton May 1st, 2008 @ 11:10 PM
Does this happen in IE only, if so I think it may be an IE issue...
Will be able to tell more when the snippet is ready :).
-
swsnider (at gmail) May 1st, 2008 @ 11:21 PM
No, we actually have only tested it in Firefox (2.x)
-
Tobie Langel May 2nd, 2008 @ 06:41 AM
- → State changed from “invalid” to “new”
-
John-David Dalton May 16th, 2008 @ 09:12 AM
- → State changed from “new” to “inactive”
Please update when you have a proper test case.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
The Prototype JavaScript library.
