Hola Amigos! AFAICT this is an issue only in the html:form tag. If we were to introduce something to trigger XHTML 1.1, couldn't we just "lie" to validator about the "name" by telling it the ID instead of the name? Would the resulting syntax emitted by validator still be ok?
Perhaps we should force XHTML 1.1 if <html:html xhtml="true" ...> or <html:xhtml/>? That seems kind of pushy to me though. Maybe in 2.0. For now, perhaps enable some sort of flag (<html:xhtml version="1.1"/>) to allow XHTML 1.1? We could poke it in pre-deprecated with a note that it's going away in 2.0. Anyhoo ... the Form tag could then check to see if it should emit XHTML (which it already does) and which version. If it's being asked to be 1.1 compliant, it could "lie" and render 'name="name"' as 'id="name"'. What do you all think? I'm listening ... If the validator would require a change, I think I might be up for fixing that as well. It's pretty well written, so I don't see modification being too large an issue. Yes, I'm aware it probably needs to stay backward-compatible, but I think I might can strategize a way to accomplish that. I'd love to hear potential hurdles you all see to accomplishing that though! Eddie --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0443-3, 10/22/2004 Tested on: 10/24/2004 9:57:21 PM avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com
