obsolete attributes "should" be ignored. I used the form name attribute as a way of knowing which AJAX module to call on behalf of that form. That allows my dofill() to serve many forms.
I've seen very few pages of any type that validates 100% and browsers accomodate this and that's one reason why there are soo many differences in how browsers act on a given page.
In this case, it was working then we started getting complaints but they were intermittent and finally we were able to narrow it down to a problem we could duplicate and once duplicated it was easy to find (but harder to fix).
By changing the doctype, none of our pages will validate at this point but that's another issue that we'll fix in the next major release.
When I posted the original question we had no idea why form.serialize was failing and still dont think it should fail even if there was a $nbsp; somewhere in the field. form.serialize should process each field and if data is present, serialize it and if not skip it. A div or field with a space should not matter.
Like I said though, the key is not just in changing the doctype but you also have to force compatibility mode. This, to me, is a greater issue as it indicates a bug somewhere in either IE9 or prototype... but regardless of where it is, it causes prototype to fail.
--
You received this message because you are subscribed to the Google Groups "Prototype &
script.aculo.us" group.