Option buttons are sometimes called ____ buttons

An HTML form is a section of a document containing normal content, markup, special elements called controls checkboxes, radio buttons, menus, etc. Users generally "complete" a form by modifying its controls entering text, selecting menu items, etc. Here's a simple form that includes labels, radio buttons, and push buttons reset the form or submit it:.

This specification includes more detailed information about forms in the subsections on form display issues. Users interact with forms through named controls. A control's "control name" is given by its name attribute. The scope of the name attribute for a control within a FORM element is the FORM element. Each control has both an initial value and a current value, both of which are character strings.

Please consult the definition of each control for information about initial values and possible constraints on values imposed by the control.

In general, a control's "initial value" may be specified with the control element's value attribute. However, the initial value of a TEXTAREA element is given by its contents, and the initial value of an OBJECT element in a form is determined by the object implementation i.

The control's "current value" is first set to the initial value. Thereafter, the control's current value may be modified through user interaction and scripts. A control's initial value does not change. Thus, when a form is reset, each control's current value is reset to its initial value.

If a control does not have an initial value, the effect of a form reset on that control is undefined. When a form is submitted for processing, some controls have their name paired with their current value and these pairs are submitted with the form. Authors should specify the scripting language of a push button script through a default script declaration with the META element.

Authors create buttons with the BUTTON element or the INPUT element. Please consult the definitions of these elements for details about specifying different button types. Authors should note that the BUTTON element offers richer rendering capabilities than the INPUT element. Several checkboxes in a form may share the same control name. Thus, for example, checkboxes allow users to select several values for the same property.

The INPUT element is used to create a checkbox control. Since user agent behavior differs, authors should ensure that in each set of radio buttons that one is initially "on". The elements used to create controls generally appear inside a FORM element, but may also appear outside of a FORM element declaration when they are used to build user interfaces.

This is discussed in the section on intrinsic events. Note that controls outside a form cannot be successful controls. The default value for this attribute is the reserved string "UNKNOWN". User agents may interpret this value as the character encoding that was used to transmit the document containing this FORM element.

The FORM element acts as a container for controls. A form can contain text and markup paragraphs, lists, etc. The following example shows a form that is to be processed by the "adduser" program when submitted. The form will be sent to the program using the HTTP "post" method. Please consult the section on form submission for information about how user agents must prepare form data for servers and how user agents should handle expected responses.

Further discussion on the behavior of servers that receive form data is beyond the scope of this specification. The control type defined by the INPUT element depends on the value of the type attribute:. Application designers should note that this mechanism affords only light security protection. Although the password is masked by user agents from casual observers, it is transmitted to the server in clear text, and may be read by anyone with low-level access to the network.

When a pointing device is used to click on the image, the form is submitted and the click coordinates passed to the server. The x value is measured in pixels from the left of the image, and the y value in pixels from the top of the image. The submitted data includes name. If the server takes different actions depending on the location clicked, users of non-graphical browsers will be disadvantaged. For this reason, authors should consider alternate approaches:. The following sample HTML fragment defines a simple form that allows the user to enter a first name, last name, email address, and gender.

When the submit button is activated, the form will be sent to the program specified by the action attribute.

In the section on the LABEL element, we discuss marking up labels such as "First name". In this next example, the JavaScript function name verify is triggered when the "onclick" event occurs:.

Please consult the section on intrinsic events for more information about scripting and events. The following example shows how the contents of a user-specified file may be submitted with a form. The user is prompted for his or her name and a list of file names whose contents should be submitted with the form. Buttons created with the BUTTON element function just like buttons created with the INPUT element, but they offer richer rendering possibilities: For example, a BUTTON element that contains an image functions like and may resemble an INPUT element whose type is set to "image", but the BUTTON element type allows content.

The following example expands a previous example, but creates submit and reset buttons with BUTTON instead of INPUT. The buttons contain images by way of the IMG element. Recall that authors must provide alternate text for an IMG element.

It is illegal to associate an image map with an IMG that appears as the contents of a BUTTON element. The SELECT element creates a menu. Each choice offered by the menu is represented by an OPTION element. A SELECT element must contain at least one OPTION element. The OPTGROUP element allows authors to group choices logically. This is particularly helpful when the user must choose from a long list of options; groups of related choices are easier to grasp and remember than a single long list of options.

In HTML 4, all OPTGROUP elements must be specified directly within a SELECT element i. Zero or more choices may be pre-selected for the user. User agents should determine which choices are pre-selected as follows:. Since user agent behavior differs, authors should ensure that each menu includes a default pre-selected OPTION. Implementors are advised that future versions of HTML may extend the grouping mechanism to allow for nested groups i.

This will allow authors to represent a richer hierarchy of choices. When rendering a menu choice , user agents should use the value of the label attribute of the OPTION element as the choice. If this attribute is not specified, user agents should use the contents of the OPTION element. The label attribute of the OPTGROUP element specifies the label for a group of choices.

In this example, we create a menu that allows the user to select which of seven software components to install. The first and second components are pre-selected but may be deselected by the user. The remaining components are not pre-selected.

The size attribute states that the menu should only have 4 rows even though the user may select from among 7 options.

The other options should be made available through a scrolling mechanism. The SELECT is followed by submit and reset buttons. Only selected options will be successful using the control name "component-select".

When no options are selected, the control is not successful and neither the name nor any values are submitted to the server when the form is submitted. Note that where the value attribute is set, it determines the control's initial value , otherwise it's the element's contents. In this example we use the OPTGROUP element to group choices. Visual user agents may allow users to select from option groups through a hierarchical menu or some other mechanism that reflects the structure of choices.

This image shows a SELECT element rendered as cascading menus. The top label of the menu displays the currently selected value PortMaster 3, 3. The user has unfurled two cascading menus, but has not yet selected the new value PortMaster 2, 3. Note that each cascading menu displays the label of an OPTGROUP or OPTION element.

The TEXTAREA element creates a multi-line text input control. User agents should use the contents of this element as the initial value of the control and should render this text initially. This example creates a TEXTAREA control that is 20 rows by 80 columns and contains two lines of text initially. The TEXTAREA is followed by submit and reset buttons.

Setting the readonly attribute allows authors to display unmodifiable text in a TEXTAREA. This differs from using standard marked-up text in a document because the value of TEXTAREA is submitted with the form. This element creates a single-line text input control. Authors should use the INPUT element to create text input controls. The ISINDEX element creates a single-line text input control that allows any number of characters.

User agents may use the value of the prompt attribute as a title for the prompt. The following ISINDEX declaration:. Currently, the semantics for ISINDEX are only well-defined when the base URI for the enclosing document is an HTTP URI. In practice, the input string is restricted to Latin-1 as there is no mechanism for the URI to specify a different character set.

Some form controls automatically have labels associated with them press buttons while most do not text fields, checkboxes and radio buttons, and menus.

For those controls that have implicit labels, user agents should use the value of the value attribute as the label string.

The LABEL element is used to specify labels for controls that do not have implicit labels,. The LABEL element may be used to attach information to controls. Each LABEL element is associated with exactly one form control.

The for attribute associates a label with another control explicitly: More than one LABEL may be associated with the same control by creating multiple references via the for attribute. This example creates a table that is used to align two text input controls and their associated labels. Each label is associated explicitly with one text input:.

This example extends a previous example form to include LABEL elements. To associate a label with another control implicitly, the control element must be within the contents of the LABEL element. In this case, the LABEL may only contain one control element.

Forms in HTML documents

The label itself may be positioned before or after the associated control. In this example, we implicitly associate two labels with two text input controls:. Note that this technique cannot be used when a table is being used for layout, with the label in one cell and its associated control in another cell.

When a LABEL element receives focus , it passes the focus on to its associated control. See the section below on access keys for examples. Labels may be rendered by user agents in a number of ways e.

The FIELDSET element allows authors to group thematically related controls and labels. Grouping controls makes it easier for users to understand their purpose while simultaneously facilitating tabbing navigation for visual user agents and speech navigation for speech-oriented user agents.

The proper use of this element makes documents more accessible. The LEGEND element allows authors to assign a caption to a FIELDSET. The legend improves accessibility when the FIELDSET is rendered non-visually.

In this example, we create a form that one might fill out at the doctor's office. It is divided into three sections: Each section contains controls for inputting the appropriate information. Note that in this example, we might improve the visual presentation of the form by aligning elements within each FIELDSET with style sheets , adding color and font information with style sheets , adding scripting say, to only open the "current medication" text area if the user indicates he or she is currently on medication , etc.

In an HTML document, an element must receive focus from the user in order to become active and perform its tasks. For example, users must activate a link specified by the A element in order to follow the specified link. Similarly, users must give a TEXTAREA focus in order to enter text into it. The tabbing order defines the order in which elements will receive focus when navigated by the user via the keyboard.

The tabbing order may include elements nested within other elements. Elements that may receive focus should be navigated by user agents according to the following rules:. The following elements support the tabindex attribute: A , AREA , BUTTON , INPUT , OBJECT , SELECT , and TEXTAREA.

In this example, the tabbing order will be the BUTTON , the INPUT elements in order note that "field1" and the button share the same tabindex, but "field1" appears later in the character stream , and finally the link created by the A element. The actual key sequence that causes tabbing navigation or element activation depends on the configuration of the user agent e. User agents may also define key sequences to navigate the tabbing order in reverse.

When the end or beginning of the tabbing order is reached, user agents may circle back to the beginning or end. Pressing an access key assigned to an element gives focus to the element.

The action that occurs when an element receives focus depends on the element. For example, when a user activates a link defined by the A element, the user agent generally follows the link. When a user activates a radio button, the user agent changes the value of the radio button.

When the user activates a text field, it allows input, etc. The following elements support the accesskey attribute: A , AREA , BUTTON , INPUT , LABEL , and LEGEND , and TEXTAREA. This example assigns the access key "U" to a label associated with an INPUT control.

Typing the access key gives focus to the label which in turn gives it to the associated control. The user may then enter text into the INPUT area. In this example, we assign an access key to a link defined by the A element. Typing this access key takes the user to another document, in this case, a table of contents. The invocation of access keys depends on the underlying system. For instance, on machines running MS Windows, one generally has to press the "alt" key in addition to the access key.

On Apple systems, one generally has to press the "cmd" key in addition to the access key. The rendering of access keys depends on the user agent. We recommend that authors include the access key in label text or wherever the access key is to apply.

User agents should render the value of an access key in such a way as to emphasize its role and to distinguish it from other characters e. In contexts where user input is either undesirable or irrelevant, it is important to be able to disable a control or render it read-only. For example, one may want to disable a form's submit button until the user has entered some required data.

Similarly, an author may want to include a piece of read-only text that must be submitted as a value along with the form.

The following sections describe disabled and read-only controls. When set, the disabled attribute has the following effects on an element:. The following elements support the disabled attribute: BUTTON , INPUT , OPTGROUP , OPTION , SELECT , and TEXTAREA. How disabled elements are rendered depends on the user agent.

Option buttons are sometimes called ____ buttons and also did the treasury make money on tarp

For example, some user agents "gray out" disabled menu items, button labels, etc. In this example, the INPUT element is disabled.

Therefore, it cannot receive user input nor will its value be submitted with the form. The only way to modify dynamically the value of the disabled attribute is through a script. The readonly attribute specifies whether the control may be modified by the user. When set, the readonly attribute has the following effects on an element:.

The following elements support the readonly attribute: The only way to modify dynamically the value of the readonly attribute is through a script. The method attribute of the FORM element specifies the HTTP method used to send the form to the processing agent. This attribute may take two values:. The "get" method should be used when the form is idempotent i. Many database searches have no visible side-effects and make ideal applications for the "get" method.

If the service associated with the processing of a form causes side effects for example, if the form modifies a database or subscription to a service , the "post" method should be used. The "get" method restricts form data set values to ASCII characters. A successful control is "valid" for submission. Every successful control has its control name paired with its current value as part of the submitted form data set.

A successful control must be defined within a FORM element and must have a control name.

If a control doesn't have a current value when the form is submitted, user agents are not required to treat it as a successful control. Hidden controls and controls that are not rendered because of style sheet settings may still be successful.

When the user submits a form e. The form data set is then encoded according to the content type specified by the enctype attribute of the FORM element.

Finally, the encoded data is sent to the processing agent designated by the action attribute using the protocol specified by the method attribute. This specification does not specify all valid submission methods or content types that may be used with forms.

However, HTML 4 user agents must support the established conventions in the following cases:. For any other value of action or method , behavior is unspecified. The enctype attribute of the FORM element specifies the content type used to encode the form data set for submission to the server. User agents must support the content types listed below. Behavior for other content types is unspecified.

Please also consult the section on escaping ampersands in URI attribute values. This is the default content type. Forms submitted with this content type must be encoded as follows:. Please consult the appendix for information about security issues for forms. The parts are sent to the processing agent in the same order the corresponding controls appear in the document stream.

Part boundaries should not occur in any of the data; how this is done lies outside the scope of this specification. User agents should supply the "Content-Type" header, accompanied by a "charset" parameter. As with all MIME transmissions, "CR LF" i. Each part may be encoded and the "Content-Transfer-Encoding" header supplied if the value of that part does not conform to the default 7BIT encoding see [RFC] , section 6. If the contents of a file are submitted with a form, the file input should be identified by the appropriate content type e.

The user agent should attempt to supply a file name for each submitted file. The file name may be specified with the "filename" parameter of the 'Content-Disposition: If the file name of the client's operating system is not in US-ASCII, the file name might be approximated or encoded using the method of [RFC].

This is convenient for those cases where, for example, the uploaded files might contain references to each other e.

Suppose we have the following form:. If the user enters "Larry" in the text input, and selects the text file "file1. If the user selected a second image file "file2. Contents Introduction to forms Controls Control types The FORM element The INPUT element Control types created with INPUT Examples of forms containing INPUT controls The BUTTON element The SELECT , OPTGROUP , and OPTION elements Pre-selected options The TEXTAREA element The ISINDEX element Labels The LABEL element Adding structure to forms: Identify the successful controls Step two: Build a form data set Step three: Encode the form data set Step four: Here's a simple form that includes labels, radio buttons, and push buttons reset the form or submit it: User agent behavior for a value other than an HTTP URI is undefined.

Possible case-insensitive values are "get" the default and "post". See the section on form submission for usage information. The client must interpret this list as an exclusive-or list, i. User agents may use this information to filter out non-conforming files when prompting a user to select files to be sent to the server cf.

This attribute has been included for backwards compatibility. Applications should use the id attribute to identify elements. Attributes defined elsewhere id , class document-wide identifiers lang language information , dir text direction style inline style information title element title target target frame information onsubmit , onreset , onclick , ondblclick , onmousedown , onmouseup , onmouseover , onmousemove , onmouseout , onkeypress , onkeydown , onkeyup intrinsic events. The default value for this attribute is "text".

It is optional except when the type attribute has the value "radio" or "checkbox". The width is given in pixels except when type attribute has the value "text" or "password". In that case, its value refers to the integer number of characters.

This number may exceed the specified size , in which case the user agent should offer a scrolling mechanism. The default value for this attribute is an unlimited number. User agents must ignore this attribute for other control types.

Option buttons are sometimes called ____ buttons

Attributes defined elsewhere id , class document-wide identifiers lang language information , dir text direction title element title style inline style information alt alternate text align alignment accept legal content types for a server readonly read-only input controls disabled disabled input controls tabindex tabbing navigation accesskey access keys usemap client-side image maps ismap server-side image maps onfocus , onblur , onselect , onchange , onclick , ondblclick , onmousedown , onmouseup , onmouseover , onmousemove , onmouseout , onkeypress , onkeydown , onkeyup intrinsic events.

In this next example, the JavaScript function name verify is triggered when the "onclick" event occurs: Creates a submit button. This is the default value. Creates a reset button.

Creates a push button. Attributes defined elsewhere id , class document-wide identifiers lang language information , dir text direction title element title style inline style information disabled disabled input controls accesskey access keys tabindex tabbing navigation onfocus , onblur , onclick , ondblclick , onmousedown , onmouseup , onmouseover , onmousemove , onmouseout , onkeypress , onkeydown , onkeyup intrinsic events.

The following is not legal HTML. Visual user agents are not required to present a SELECT element as a list box; they may use any other mechanism, such as a drop-down menu. If not set, the SELECT element only permits single selections. Attributes defined elsewhere id , class document-wide identifiers lang language information , dir text direction title element title style inline style information disabled disabled input controls tabindex tabbing navigation onclick , ondblclick , onmousedown , onmouseup , onmouseover , onmousemove , onmouseout , onkeypress , onkeydown , onkeyup intrinsic events.

Attributes defined elsewhere id , class document-wide identifiers lang language information , dir text direction title element title style inline style information disabled disabled input controls onclick , ondblclick , onmousedown , onmouseup , onmouseover , onmousemove , onmouseout , onkeypress , onkeydown , onkeyup intrinsic events. OPTION Attribute definitions selected [CI] When set, this boolean attribute specifies that this option is pre-selected.

If this attribute is not set, the initial value is set to the contents of the OPTION element. When specified, user agents should use the value of this attribute rather than the content of the OPTION element as the option label.

None PortMaster 3 3. A graphical user agent might render this as: Users should be able to enter more lines than this, so user agents should provide some means to scroll through the contents of the control when the contents extend beyond the visible area. Users should be able to enter longer lines than this, so user agents should provide some means to scroll through the contents of the control when the contents extend beyond the visible area.

User agents may wrap visible text lines to keep long lines visible without the need for scrolling. Attributes defined elsewhere id , class document-wide identifiers lang language information , dir text direction title element title style inline style information readonly read-only input controls disabled disabled input controls tabindex tabbing navigation onfocus , onblur , onselect , onchange , onclick , ondblclick , onmousedown , onmouseup , onmouseover , onmousemove , onmouseout , onkeypress , onkeydown , onkeyup intrinsic events.

Second line of initial text. This attribute specifies a prompt string for the input field. Attributes defined elsewhere id , class document-wide identifiers lang language information , dir text direction title element title style inline style information.

The following ISINDEX declaration: When present, the value of this attribute must be the same as the value of the id attribute of some other control in the same document. When absent, the label being defined is associated with the element's contents. Attributes defined elsewhere id , class document-wide identifiers lang language information , dir text direction title element title style inline style information accesskey access keys onfocus , onblur , onclick , ondblclick , onmousedown , onmouseup , onmouseover , onmousemove , onmouseout , onkeypress , onkeydown , onkeyup intrinsic events.

Each label is associated explicitly with one text input: In this example, we implicitly associate two labels with two text input controls: This attribute specifies the position of the legend with respect to the fieldset.

The legend is at the top of the fieldset. The legend is at the bottom of the fieldset. The legend is at the left side of the fieldset. The legend is at the right side of the fieldset.

Attributes defined elsewhere id , class document-wide identifiers lang language information , dir text direction title element title style inline style information accesskey access keys onclick , ondblclick , onmousedown , onmouseup , onmouseover , onmousemove , onmouseout , onkeypress , onkeydown , onkeyup intrinsic events.

This value must be a number between 0 and User agents should ignore leading zeros. An access key is a single character from the document character set. Authors should consider the input method of the expected reader when specifying an accesskey. Attribute definitions disabled [CI] When set for a form control, this boolean attribute disables the control for user input. Attribute definitions readonly [CI] When set for a form control, this boolean attribute prohibits changes to the control.