[Bug 13054] New: I am referring to this section of the HTML5 spec: http://www.w3.org/TR/html5/association-of-controls-and-forms.html#association-of-controls-and-forms Decoupling form controls and the form element is a good first step to improving the flexibility of web fo

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13054

           Summary: I am referring to this section of the HTML5 spec:
                    http://www.w3.org/TR/html5/association-of-controls-and
                    -forms.html#association-of-controls-and-forms
                    Decoupling form controls and the form element is a
                    good first step to improving the flexibility of web fo
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Specification: http://www.w3.org/TR/html5/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
I am referring to this section of the HTML5 spec:

http://www.w3.org/TR/html5/association-of-controls-and-forms.html#association-
of-controls-and-forms

Decoupling form controls and the form element is a good first step to
improving the flexibility of web forms, but I think we should go one step
further: allowing a single form-associated element to be associated with
multiple forms. I propose that there may be circumstances where application
developers may want to create a form containing several inputs, but to also
associate sub-groups of those inputs with another form.

I propose that the syntax of the form attribute be modified to work like the
class attribute does. rather than containing a single form id, the form
attribute should be a space-separated list of form ids.

I recognize some difficulties in this approach, for example:
- Submit inputs and buttons obviously cannot attempt to submit multiple forms
at once, so the proposed syntax should be invalid for those elements.

- When clearing a form which contains an input that is associated with a
second form, it is unclear what the expected behavior of that input would be.
Should the input be cleared, or remain populated?

I think good solutions can be found for these problems, and, if there is
interest among the group, this new syntax could be adopted and may prove
useful to many developers.

Thanks for reading. I hope I made my case well. 

Posted from: 71.61.178.237
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_7) AppleWebKit/535.1
(KHTML, like Gecko) Chrome/13.0.782.24 Safari/535.1

-- 
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 Saturday, 25 June 2011 07:48:08 UTC