- From: <bugzilla@jessica.w3.org>
- Date: Mon, 07 Mar 2011 06:41:42 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12241 John Thomas <therandshow@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |therandshow@gmail.com --- Comment #2 from John Thomas <therandshow@gmail.com> 2011-03-07 06:41:40 UTC --- Let me throw this out there. I find unassociated form elements on occasion very useful. For example, if I want form elements that trigger javascript behavior but that I don't wanted submitted anywhere. To abstract this a little, the issue isn't that I don't want unassociated form elements, it's that I don't want the form elements associated with anything on the server as the role of these form elements is purely a matter of browser interaction, however, when you're dealing with form elements that are never meant to interact with a server, does the form tag still have relevance? Now that doesn't answer the question, because you could always just throw input elements outside the form tags. But on the other hand that can lead to serious issues with CSS + here's a scenario: You have a select with the name "choice": cars a computer a rocking chair when someone selects "cars" it triggers a dependent drop down, and now you want the value of the dependent dropdown to be associated with "choice" for that form. However if someone selects "a computer" or "a rocking chair", the original drop down should still be associated. In this situation being able to turn on and off the association of a form element would be very useful, and thus being able to do selectTag.form="" would be nice -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 7 March 2011 06:41:43 UTC