This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In most of the cases we used to have some label and the input elements while doing the layout. Currently there is no possibility to define the label control as part of the input control. Meaning, I need to define a label and a input control separately. Instead I need to able to define the label value as part of the input control. And more over if i define the input field is 'required', then some * mark should be added before the label control. From my perspective this is the common use case in most of the web application.
What are the actual problems caused by the current situation? That is, what about the current situation is bad, such that you "need to be able to define the label value as part of the input control"?
(In reply to comment #1) > What are the actual problems caused by the current situation? That is, what > about the current situation is bad, such that you "need to be able to define > the label value as part of the input control"? <input id="name" name="name" autocomplete=off value="" /> This is definition for an input control. Usually we will have some label control before this input control. <label for="name">Name: *</label> <input id="name" name="name" autocomplete=off value="" /> In that case, I should be able to define the label value as part of the input control. <input id="name" name="name" autocomplete=off value="" label="Name:" /> Then based on the required attribute, My label control should be added with * mark. Otherwise it should render only the label value. I hope this would clarify your doubts.
No, that just shows what you want to do. What's much more important is *why* you want to do that - what problem are you having that can't be easily solved using existing HTML?
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: see comment 3
mass-move component to LC1