An HTML element is an individual component of an HTML HTML, which stands for HyperText Markup Language, is the predominant markup language for web pages. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It allows images and objects to be embedded and can be used to create interactive forms document. HTML documents are composed of a tree A tree structure is a way of representing the hierarchical nature of a structure in a graphical form. It is named a "tree structure" because the classic representation resembles a tree, even though the chart is generally upside down compared to an actual tree, with the "root" at the top and the "leaves" at the bottom of HTML elements and other nodes A node is an abstract basic unit used to build linked data structures such as trees, linked lists, and computer-based representations of graphs. Each node contains some data and possibly links to other nodes. Links between nodes are often implemented by pointers or references, such as text nodes. Each element can have attributes HTML, which stands for HyperText Markup Language, is the predominant markup language for web pages. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It allows images and objects to be embedded and can be used to create interactive forms specified. Elements can also have content, including other elements and text. HTML elements represent semantics Semantics is the study of meaning, usually in language. The word "semantics" itself denotes a range of ideas, from the popular to the highly technical. It is often used in ordinary language to denote a problem of understanding that comes down to word selection or connotation. This problem of understanding has been the subject of many, or meaning. For example, the title element represents the title of the document.

In the HTML syntax, most elements are written with a start tag and an end tag, with the content in between. Tags are composed of the name of the element, surrounded by angle brackets Brackets are tall punctuation marks used in matched pairs within text, to set apart or interject other text. In the United States, "bracket" usually refers specifically to the "square" or "box" type; in British usage, it normally refers to a parenthesis mark. An end tag also has a slash after the opening angle bracket, to distinguish it from the start tag. For example, a paragraph, which is represented by the p element, would be written as

<p>In the HTML syntax, most elements are written ...</p>

However, not all of these elements require the end tag, or even the start tag, to be present. Some elements, the so-called void elements don't have an end tag. A typical example is the br element, which represents a significant line break, such as in a poem or an address. For example, the address of the dentist in Finding Nemo Finding Nemo is a 2003 American computer-animated film written by Andrew Stanton, directed by Stanton and Lee Unkrich and produced by Pixar Animation Studios for Walt Disney Pictures. It tells the story of the overly protective clownfish Marlin, voiced by Albert Brooks, who along with a regal tang called Dory, voiced by Ellen DeGeneres, searches would be written as

<p>P. Sherman<br>42 Wallaby Way<br>Sydney</p>

Attributes are specified on the start tag. For example, the abbr element, which represents an abbreviation An abbreviation is a shortened form of a word or phrase. Usually, but not always, it consists of a letter or group of letters taken from the word or phrase. For example, the word abbreviation can itself be represented by the abbreviation abbr., abbrv. or abbrev, expects a title attribute with its expansion. This would be written as

<abbr title="Hyper Text Markup Language">HTML</abbr>

Contents 1 Overview 1.1 Syntax 1.2 Element standards 1.3 Element status 1.4 Presentation and behaviour 2 Document structure elements 3 Document head elements 4 Document body elements 4.1 Block elements 4.1.1 Basic text 4.1.2 Lists 4.1.3 Other block elements 4.2 Inline elements 4.2.1 Anchor 4.2.2 Phrase elements 4.2.2.1 General 4.2.2.2 Computer phrase elements 4.2.2.3 Presentation 4.2.3 Span 4.2.4 Other inline elements 4.3 Images and objects 4.4 Forms 4.5 Tables 5 Frames 6 Historic elements 7 Non-standard elements 8 Comments 9 References 10 Bibliography 10.1 HTML standards 10.2 Other sources 11 External links

Overview

Syntax

Parts of an HTML container element:

• Start tag: <p … >
  • Attribute:
    • name: class
    • value: foo
• Content: This is a paragraph.
• End tag: </p>

complete: <p class="foo">This is a paragraph</p>

There are multiple kinds of HTML elements: void elements, raw text elements, and normal elements.

Void elements only have a start tag, which contains any attributes. One example is the link element, for which the syntax is

<link rel=stylesheet href=fancy.css type="text/css">

This link element points the browser at a stylesheet to use when presenting the HTML document to the user. Note that in the HTML syntax, attributes don't have to be quoted. When using the XML XML is a set of rules for encoding documents in machine-readable form. It is defined in the XML 1.0 Specification produced by the W3C, and several other related specifications, all gratis open standards syntax (XHTML XHTML is a family of XML markup languages that mirror or extend versions of the widely used Hypertext Markup Language (HTML), the language in which web pages are written), on the other hand, all attributes must be quoted, and a trailing slash is required before the last angle bracket:

<link rel="stylesheet" href="fancy.css" type="text/css" />

Raw text elements are constructed with:

• a start tag (<tag>) marking the beginning of an element, which may incorporate any number of attributes HTML, which stands for HyperText Markup Language, is the predominant markup language for web pages. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It allows images and objects to be embedded and can be used to create interactive forms;
• some amount of text content, but no elements (all tags, apart from the applicable end tag, will be interpreted as content);
• an end tag, in which the element name is prepended with a forward slash The slash is a sign, "/", used as punctuation mark and for various other purposes. It is often called a forward slash and many other alternative names: </tag>. In some versions of HTML, the end tag is optional for some elements. The end tag is required in XHTML.

Normal elements usually have both a start tag and an end tag, although for some elements the end tag, or both tags, can be omitted. It is constructed in a similar way:

• a start tag (<tag>) marking the beginning of an element, which may incorporate any number of attributes HTML, which stands for HyperText Markup Language, is the predominant markup language for web pages. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It allows images and objects to be embedded and can be used to create interactive forms;
• some amount of content, including text and other elements;
• an end tag, in which the element name is prepended with a forward slash The slash is a sign, "/", used as punctuation mark and for various other purposes. It is often called a forward slash and many other alternative names: </tag>.

Attributes define desired behavior or indicate additional element properties. Most attributes require a value. In HTML, the value can be left unquoted if it doesn't include spaces (name=value), or it can be quoted with single or double quotes (name='value' or name="value"). In XML, those quotes are required. Boolean attributes, on the other hand, don't require a value to be specified. An example is the checked for checkboxes:

<input type=checkbox checked>

In the XML syntax, though, the name should be repeated as the value:

<input type="checkbox" checked="checked"/>

Informally, HTML elements are sometimes referred to as "tags" (an example of synecdoche Synecdoche is closely related to metonymy ; indeed, synecdoche is sometimes considered a subclass of metonymy. It is more distantly related to other figures of speech, such as metaphor), though many prefer the term tag strictly in reference to the markup delimiting the start and end of an element.

Element (and attribute) names may be written in any combination of upper or lower case in HTML, but must be in lower case in XHTML.^[1] The canonical form was upper-case until HTML 4, and was used in HTML specifications, but in recent years, lower-case has become more common.

Element standards

HTML elements are defined in a series of freely-available open standards issued since 1995, initially by the IETF The Internet Engineering Task Force develops and promotes Internet standards, cooperating closely with the W3C and ISO/IEC standards bodies and dealing in particular with standards of the TCP/IP and Internet protocol suite. It is an open standards organization, with no formal membership or membership requirements. All participants and managers are and subsequently by the W3C The World Wide Web Consortium is the main international standards organization for the World Wide Web (abbreviated WWW or W3).

Since the early 1990s, manufacturers of user agents A user agent is the client application used with a particular network protocol; the phrase is most commonly used in reference to those which access the World Wide Web. Other systems, such as Session Initiation Protocol , use the term user agent to refer to both end points of a phone call, server and client (e.g. web browsers A web browser is a software application for retrieving, presenting, and traversing information resources on the World Wide Web. An information resource is identified by a Uniform Resource Identifier and may be a web page, image, video, or other piece of content. Hyperlinks present in resources enable users to easily navigate their browsers to) have often developed their own elements, some of which have been adopted in later standards. Other user agents may not recognise non-standard elements, and they may be ignored or displayed improperly.

In 1998, XML XML is a set of rules for encoding documents in machine-readable form. It is defined in the XML 1.0 Specification produced by the W3C, and several other related specifications, all gratis open standards (a simplified form of SGML) introduced mechanisms to allow anyone to develop their own elements and incorporate them in XHTML documents, for use with XML-aware user agents.^[2]

Subsequently, HTML 4.01 was rewritten in an XML-compatible form, XHTML 1.0 (eXtensible HTML). The elements in each are identical, and in most cases valid XHTML 1.0 documents will be valid or nearly-valid HTML 4.01 documents. This article mainly focuses on real HTML, unless noted otherwise; however, it remains applicable to XHTML. (See HTML HTML, which stands for HyperText Markup Language, is the predominant markup language for web pages. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It allows images and objects to be embedded and can be used to create interactive forms for a discussion of the minor differences between the two).

Element status

Since the first version of HTML, several elements have become outmoded, and are deprecated In computer software or authoring programs standards and documentation, the term deprecation is applied to software features that are superseded and should be avoided. Although deprecated features remain in the current version, their use may raise warning messages recommending alternative practices, and deprecation may indicate that the feature in later standards, or do not appear at all, in which case they are invalid (and will be found invalid, and perhaps not displayed, by validating XML validation is the process of checking a document written in XML to confirm that it is both "well-formed" and also "valid" in that it follows a defined structure. A "well-formed" document follows the basic syntactic rules of XML, which are the same for all XML documents. A valid document also respects the rules user agents).^[3]

At present, the status of elements is complicated by the existence of three types of HTML 4.01 / XHTML 1.0 DTD:

• Transitional, which contain deprecated elements, but which were intended to provide a transitional period during which authors could update their practices;
• Frameset, which are versions of the Transitional DTDs which also allow authors to write frameset documents;
• Strict, which is the up-to date (as at 1999 1999 was a common year that started on a Friday (link will display full calendar). In the Gregorian calendar, it was the 1999th year of the Common Era, or of Anno Domini; the 999th year of the 2nd millennium; and the 99th year of the 20th century. It was also the 10th and last year of the 1990s) form of HTML.

The first Standard (HTML 2.0 HTML, which stands for HyperText Markup Language, is the predominant markup language for web pages. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It allows images and objects to be embedded and can be used to create interactive forms) contained four deprecated elements, one of which was invalid in HTML 3.2 HTML, which stands for HyperText Markup Language, is the predominant markup language for web pages. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It allows images and objects to be embedded and can be used to create interactive forms. All four are invalid in HTML 4.01 Transitional HTML, which stands for HyperText Markup Language, is the predominant markup language for web pages. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It allows images and objects to be embedded and can be used to create interactive forms, which also deprecated a further ten elements. All of these, plus two others, are invalid in HTML 4.01 Strict HTML, which stands for HyperText Markup Language, is the predominant markup language for web pages. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It allows images and objects to be embedded and can be used to create interactive forms. While the frame elements are still current in the sense of being present in the Transitional and Frameset DTDs, there are no plans to preserve them in future standards, as their function has been largely replaced, and they are highly problematic for user accessibility.

(Strictly speaking, the most recent XHTML standard, XHTML 1.1 XHTML is a family of XML markup languages that mirror or extend versions of the widely used Hypertext Markup Language (HTML), the language in which web pages are written (2001 2001 was a common year that started on a Monday. In the Gregorian Calendar, it was the 2001st year of the Common Era or the Anno Domini designation. 2001 was also the first year of the Third millennium and of the 21st century as there was no year zero in the Gregorian calendar. However, popular culture views 2000 as holding this distinction), does not include frames at all; it is approximately equivalent to XHTML 1.0 Strict, but also includes the Ruby markup Ruby characters are small, annotative glosses that can be placed above or to the right of a Chinese character when writing languages with logographic characters such as Chinese or Japanese to show the pronunciation. Typically called just ruby or rubi, such annotations are usually used as a pronunciation guide for relatively obscure characters module.)^[4]

A common source of confusion is the loose use of deprecated to refer to both deprecated and invalid status, and to elements which are expected to be formally deprecated in future.

Presentation and behaviour

In keeping with the principle of separation of concerns In computer science, separation of concerns is the process of separating a computer program into distinct features that overlap in functionality as little as possible. A concern is any piece of interest or focus in a program. Typically, concerns are synonymous with features or behaviors. Progress towards SoC is traditionally achieved through, the function of HTML is primarily to add structural and semantic Semantics is the study of meaning, usually in language. The word "semantics" itself denotes a range of ideas, from the popular to the highly technical. It is often used in ordinary language to denote a problem of understanding that comes down to word selection or connotation. This problem of understanding has been the subject of many information to the raw text of a document. Presentation and behaviour Behavior, or behaviour , refers to the actions of an organism or system, usually in relation to its environment, which includes the other organisms or systems around as well as the physical environment. It is the response of the organism or system to various stimuli or inputs, whether internal or external, conscious or subconscious, overt or are separate functions, which can be added as desired, ideally through links to external documents such as stylesheets Web style sheets are a form of separation of presentation and content for web design in which the markup of a webpage contains the page's semantic content and structure, but does not define its visual layout (style). Instead, the style is defined in an external stylesheet file using a style sheet language such as CSS or XSL. This design approach, graphics Graphics are visual presentations on some surface, such as a wall, canvas, computer screen, paper, or stone to brand, inform, illustrate, or entertain. Examples are photographs, drawings, Line Art, graphs, diagrams, typography, numbers, symbols, geometric designs, maps, engineering drawings, or other images. Graphics often combine text, files, and scripts Client-side scripting generally refers to the class of computer programs on the web that are executed client-side, by the user's web browser, instead of server-side . This type of computer programming is an important part of the Dynamic HTML (DHTML) concept, enabling web pages to be scripted; that is, to have different and changing content.

This allows the document to be presented by different user agents according to their purposes and abilities; for example, a user agent can select an appropriate stylesheet to present a document by displaying on a monitor, printing on paper, or to determine speech characteristics in an aural user agent. The structural and semantic functions of the markup remain identical in each case.

Historically, user agents did not always support these features. In the 1990s, as a stop-gap, presentational elements were added to HTML, at the cost of creating problems for interoperability and user accessibility. This is now regarded as outmoded and has been superseded by stylesheet-based design; most presentational elements are now deprecated.^[5]

External image files are incorporated with the img or object elements. (With XHTML, the SVG Scalable Vector Graphics is a family of specifications of an XML-based file format for describing two-dimensional vector graphics, both static and dynamic (i.e. interactive or animated) language can also be used to write graphics within the document, though linking to external SVG files is generally simpler.)^[6] Where an image is not purely decorative, HTML allows replacement content with similar semantic value to be provided for non-visual user agents.

An HTML document can also be extended through the use of scripts to provide additional behaviours beyond the abilities of HTML hyperlinks and forms.

The elements style and script, with related attributes, provide reference points in HTML markup for links to stylesheets and scripts. They can also contain instructions directly.

• In the document head, script and style may either link to shared external documents, or contain embedded instructions. (The link element can also be used to link stylesheets.)
• The style attribute is valid in most document body elements for inclusion of inline style instructions.
• Event-handling attributes, which provide links to scripts, are optional in most elements.
• script can occur at any point in the document body.
• For user agents which do not operate scripts, the noscript element provides alternative content where appropriate; however, it can only be used as a block-level element.

Document structure elements

<html>...</html>

The Root element Each XML document has exactly one single root element. This element is also known as the document element. It encloses all the other elements and is therefore the sole parent element to all the other elements of an HTML document; all other elements are contained in this.

The HTML element delimits the beginning and the end of an HTML document.

Standardised in HTML 2.0; still current.

<head>...</head>

Container for processing information and metadata for an HTML document.

Standardised in HTML 2.0; still current.

(See Document head elements for child elements.)

<body>...</body>

Container for the displayable content of an HTML document.

Standardised in HTML 2.0; still current.

(See Document body elements for child elements.)

Document head elements

<base>

Specifies a base URL In computing, a Uniform Resource Locator is a Uniform Resource Identifier (URI) that specifies where an identified resource is available and the mechanism for retrieving it. In popular usage and in many technical documents and verbal discussions it is often incorrectly used as a synonym for URI,. The best-known example of a URL is the " for all relative href and other links in the document. Must appear before any element that refers to an external resource. HTML permits only one base element for each document. The base element has attributes, but no contents.

A development version of BASE is mentioned in HTML Tags; standardised in HTML 2.0; still current.

<basefont> (deprecated)

Specifies a base font size, typeface, and color for the document. Used together with font elements. Deprecated In computer software or authoring programs standards and documentation, the term deprecation is applied to software features that are superseded and should be avoided. Although deprecated features remain in the current version, their use may raise warning messages recommending alternative practices, and deprecation may indicate that the feature in favor of stylesheets Web style sheets are a form of separation of presentation and content for web design in which the markup of a webpage contains the page's semantic content and structure, but does not define its visual layout (style). Instead, the style is defined in an external stylesheet file using a style sheet language such as CSS or XSL. This design approach.

Standardised in HTML 3.2; deprecated in HTML 4.0 Transitional; invalid in HTML 4.0 Strict.

<isindex> (deprecated)

isindex could either appear in the document head or in the body, but only once in a document. Requires a server-side search engine.

In the head, indicates that the document is a searchable index. Visually presents a one-line text input for keyword entry. When submitted, the query string In World Wide Web, a query string is the part of a Uniform Resource Locator that contains data to be passed to web applications such as CGI programs is appended to the current URL In computing, a Uniform Resource Locator is a Uniform Resource Identifier (URI) that specifies where an identified resource is available and the mechanism for retrieving it. In popular usage and in many technical documents and verbal discussions it is often incorrectly used as a synonym for URI,. The best-known example of a URL is the " and the document is displayed with these keywords highlighted. Generally if the server supports this feature it will add the isindex elements to documents without author intervention.

ISINDEX existed in HTML Tags; standardised in HTML 2.0; deprecated in HTML 4.0 Transitional; invalid in HTML 4.0 Strict.

<link>

Specifies links to other documents, such as previous and next links, or alternate versions.^[7] A common use is to link to external stylesheets Cascading Style Sheets is a style sheet language used to describe the presentation semantics (that is, the look and formatting) of a document written in a markup language. Its most common application is to style web pages written in HTML and XHTML, but the language can also be applied to any kind of XML document, including SVG and XUL, using the form:

<link rel="stylesheet" type="text/css" href="url" title="description_of_style">^[8]

A less-common, but important, usage is to supply navigation hints consistently through use of microformats A microformat is a web-based approach to semantic markup that seeks to re-use existing HTML/XHTML tags to convey metadata and other attributes, in web pages and other contexts that support (X)HTML, such as RSS. This approach allows information intended for end-users (such as contact information, geographic coordinates, calendar events, and the. Several common relationships are defined, that may be exposed to users through the browser interface rather than directly in the web page.

<link rel="next" href="url">

A document’s head element may contain any number of link elements. The link element has attributes, but no contents.

LINK existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

<meta> Meta elements are HTML or XHTML elements used to provide structured metadata about a Web page. Such elements must be placed as tags in the< code>head section of an HTML or XHTML document. Meta elements can be used to specify page description, keywords and any other metadata not provided through the other head elements and attributes

Can be used to specify additional metadata Metadata is loosely defined as data about data. Though this definition is easy to remember, it is not very precise. The strength of this definition is in recognizing that metadata is data. As such, metadata can be stored and managed in a database, often called a registry or repository. However, it is impossible to identify metadata just by looking about a document, such as its author, publication date, expiration date, page description, keywords, or other information not provided through the other header elements and attributes. Because of their generic nature, meta elements specify associative key-value pairs An associative array is an abstract data type composed of a collection of unique keys and a collection of values, where each key is associated with one value (or set of values). The operation of finding the value associated with a key is called a lookup or indexing, and this is the most important operation supported by an associative array. The.

In one form, meta elements can specify HTTP The Hypertext Transfer Protocol is an Application Layer protocol for distributed, collaborative, hypermedia information systems headers which should be sent by a web server before the actual content, for example:

<meta http-equiv="foo" content="bar">

— this specifies that the page should be served with an HTTP header called foo that has a value bar.

In the general form, a meta element specifies name and associated content attributes describing aspects of the HTML page. To prevent possible ambiguity, an optional third attribute, scheme, may be supplied to specify a semantic framework that defines the meaning of the key and its value: for example:

<meta name="foo" content="bar" scheme="DC">

In this example, the meta element identifies itself as containing the foo element, with a value of bar, from the DC or Dublin Core resource description framework.

Standardised in HTML 2.0; still current.

<object>…</object>

Used for including generic objects within the document header. Though rarely used within a head element, it could potentially be used to extract foreign data and associate it with the current document.

Standardised in HTML 4.0; still current.

<script>…</script>

Can act as a container for script instructions or link to an external script with the optional src attribute.^[9] Also usable in the document body to dynamically generate either both block or inline content.

Standardised in HTML 3.2; still current.

<style>…</style>

Specifies a style for the document, usually in the form:

<style type="text/css"> … </style>

Can either act as a container for style instructions or link to external stylesheets – for example, in CSS, with @import directives of the form:

<style> @import url; </style>^[10]

Standardised in HTML 3.2; still current.

<title>…</title>

Define a document title. Required in every HTML and XHTML document. User agents may use the title in different ways. For example:

• Web browsers usually display it in a window’s title bar when the window is open, and (where applicable) in the task bar when the window is minimized.
• It may become the default filename when saving the page.
• Search engines’ web crawlers may pay particular attention to the words used in the title.

The title element must not contain other elements, only text. Only one title element is permitted in a document.

TITLE existed in HTML Tags, and was standardised in HTML 2.0; still current.

Document body elements

In visual browsers, displayable elements can be rendered as either block or inline. While all elements are part of the document sequence, block elements appear within their parent elements:

• as rectangular objects which do not break across lines;
• with block margins, width and height properties which can be set independently of the surrounding elements.

Conversely, inline elements are treated as part of the flow of document text; they cannot have margins, width or height set, and do break across lines.

Block elements

Basic text

<p>…</p>

Creates a paragraph, perhaps the most common block level element.

P existed in HTML Tags, and was standardised in HTML 2.0; still current.

<h1>…</h1> <h2>…</h2> <h3>…</h3> <h4>…</h4> <h5>…</h5> <h6>…</h6>

Section headings at different levels. <h1> delimits the highest-level heading, <h2> the next level down (sub-section), <h3> for a level below that, and so on to <h6>.

Most visual browsers show headings as large bold text by default, though this can be overridden with CSS. Heading elements are not intended merely for creating large or bold text — they describe the document’s structure and organization. Some programs use them to generate outlines and tables of contents.

Headings existed in HTML Tags, and were standardised in HTML 2.0; still current.

Lists

<dl>…</dl>

A definition list (consisting of definition terms paired with definitions).

DL existed in HTML Tags, and was standardised in HTML 2.0; still current.

<dt>…</dt>

A definition term in a definition list.

DT existed in HTML Tags, and was standardised in HTML 2.0; still current.

<dd>…</dd>

The definition of a term, in a definition list.

DD existed in HTML Tags, and was standardised in HTML 2.0; still current.

<ol>…</ol>

An ordered (enumerated) list. The type attribute can be used to specify the kind of ordering, but stylesheets give more control: {list-style-type: foo}. The default is Arabic numbering.

OL existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

<ul>…</ul>

An unordered (bulleted) list. Stylesheets can be used to specify the list marker: {list-style-type: foo}. The default marker is a disc.

UL existed in HTML Tags, and was standardised in HTML 2.0; still current.

<li>…</li>

A list item in ordered (ol) or unordered (ul) lists.

LI existed in HTML Tags, and was standardised in HTML 2.0; still current.

<dir>…</dir> (deprecated)

A directory listing. The original purpose of this element was never widely supported; deprecated in favor of <ul>.

DIR existed in HTML Tags, and was standardised in HTML 2.0; deprecated in HTML 4.0 Transitional; invalid in HTML 4.0 Strict.

<menu>…</menu> (deprecated)

A menu listing. Should be more compact than an <ul> list, but badly supported. Deprecated in favor of <ul>.

MENU existed in HTML Tags, and was standardised in HTML 2.0; deprecated in HTML 4.0 Transitional; invalid in HTML 4.0 Strict.

Other block elements

<address>…</address>

Contact information for the document author.

ADDRESS existed in HTML Tags, and was standardised in HTML 2.0; still current.

<blockquote>…</blockquote>

A block-level quotation, for when the quotation includes block level elements, e.g. paragraphs. The cite attribute may give the source, and must be a fully qualified Uniform Resource Identifier.

The default presentation of block quotations in visual browsers is usually to indent them from both margins. This has led to the element being unnecessarily used just to indent paragraphs, regardless of semantics. For quotations not containing block level elements see the quote (q) element.

BLOCKQUOTE existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current. See blockquote element for more information.

<center>…</center> (deprecated)

Creates a block-level center-aligned division. Deprecated in favor of <div> or another element with centering defined using stylesheets.

Standardised in HTML 3.2; deprecated in HTML 4.0 Transitional; invalid in HTML 4.0 Strict.

<del>...</del>

Marks a deleted section of content. This element can also be used as inline.

Standardised in HTML 4.0; still current.

<div>…</div>

Main article: Span and div

A block-level logical division. A generic element with no semantic meaning used to distinguish a document section, usually for purposes such as presentation or behaviour controlled by stylesheets or DOM calls.

Proposed in the HTML 3.0 Drafts; Standardised in HTML 3.2; still current.

<hr>

A horizontal rule. Presentational rules can also be drawn with stylesheets.

Proposed in the HTML 3.0 Drafts; Standardised in HTML 3.2; still current.

<ins>...</ins>

Marks a section of inserted content. This element can also be used as inline.

Standardised in HTML 4.0; still current.

<noscript>...</noscript>

Replacement content for scripts. Unlike script this can only be used as a block-level element.

Standardised in HTML 4.0; still current.

<pre>…</pre>

Pre-formatted text. Text within this element is typically displayed in a non-proportional font exactly as it is laid out in the file (see ASCII art). Whereas browsers ignore whitespace for other HTML elements, in pre, whitespace should be rendered as authored. (With the CSS properties: {white-space: pre; font-family: monospace;}, other elements can be presented in the same way.) This element can contain any inline element except: image (IMG), object (OBJECT), big font size (BIG), small font size (SMALL), superscript (SUP), and subscript (SUB).

PRE existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

<script>...</script>

Places a script in the document. Also usable in the head and in inline contexts.

Note: SCRIPT is not itself either a block or inline element; by itself it should not display at all, but it can contain instructions to dynamically generate either both block or inline content.

Standardised in HTML 3.2; still current.

Inline elements

Inline elements cannot be placed directly inside the body element; they must be wholly nested within block-level elements ^[11].

Anchor

<a>…</a>

An anchor element is called an anchor because web designers can use it to anchor a URL to some text on a web page. When users view the web page in a browser, they can click the text to activate the link and visit the page whose URL is in the link.^[12]

In HTML, an anchor can be either the origin or the target (destination) end of a hyperlink.

With the attribute href (hypertext reference [1]), the anchor becomes a hyperlink to either another part of the document or another resource (e.g. a webpage) using an external URL.

Alternatively (and sometimes concurrently), with the name or id attributes set, the element becomes a target. A Uniform Resource Locator can link to this target via a fragment identifier. Any element can now be made into an anchor by using the id attribute,[2] so using <a name="foo"> is not necessary.

The attribute title may be set to give brief information about the link:

<a href="URL" title="additional information">link text</a>

In most graphical browsers, when the cursor hovers over a link, it typically changes into a hand with a stretched index finger, and the title appears in some way (varies according to browser). Some browsers render alt text the same way, though this is technically incorrect.

A existed in HTML Tags, and was standardised in HTML 2.0; still current.

Phrase elements

General

<abbr>…</abbr>

Marks an abbreviation, and can make the full form available:

<abbr title="abbreviation">abbr.</abbr>

Standardised in HTML 4.0; still current.

<acronym>…</acronym>

Similar to the abbr element, but marks an acronym:

<acronym title="Hyper-Text Markup Language">HTML</acronym>

Standardised in HTML 4.0; still current.

<dfn>…</dfn>

Inline definition of a single term.

DFN existed in HTML Internet Draft 1.2, and was fully standardised in HTML 3.2; still current.

<em>…</em>

Emphasis (conventionally displayed in italics)

EM existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

<strong>…</strong>

strong emphasis (conventionally displayed bold).

An aural user agent may use different voices for emphasis.

STRONG existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

Computer phrase elements

These elements are useful primarily for documenting computer code development and user interaction through differentiation of source code (<code>), source code variables (<var>), user input (<kbd>), and terminal output (<samp>).

<code>…</code>

A code snippet. Conventionally rendered in a monospace font: Code snippet.

CODE existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

<samp>…</samp>

Sample output (from a program or script)

SAMP existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

<kbd>…</kbd>

Keyboard - text to be entered by the user

KBD existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

<var>…</var>

Variable

VAR existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

Presentation

As visual presentational markup only applies directly to visual browsers, its use is discouraged. Stylesheets should be used instead. Several of these elements are deprecated or invalid in HTML 4 / XHTML 1.0, and the remainder are invalid in the current draft of XHTML 2.0. The current draft of HTML 5, however, includes <b>, <i>, and <small>.

<b>…</b>

Sets font to boldface where possible. (Equivalent CSS: {font-weight: bold}.) <strong>...</strong> usually has the same effect in visual browsers, as well as having more semantic meaning.

B existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

<i>…</i>

Sets font to italic where possible. (Equivalent CSS: {font-style: italic}.) <em>...</em> usually has the same effect in visual browsers, as well as having more semantic meaning.

I existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

<big>…</big>

Increases font size (bigger text). Equivalent CSS: {font-size: larger}

Standardised in HTML 3.2; still current.

<small>…</small>

Decreases font size (smaller text). Equivalent CSS: {font-size: smaller}

Standardised in HTML 3.2; still current.

<strike>…</strike> (deprecated) and <s>…</s> (deprecated)

Strike-through text (Strikethrough), (Equivalent CSS: {text-decoration: line-through})

STRIKE was standardised in HTML 3.2; deprecated in HTML 4.0 Transitional; invalid in HTML 4.0 Strict.

S is deprecated in HTML 4.0 Transitional (having not appeared in any previous standard), and is invalid in HTML 4.0 Strict.

<tt>…</tt>

Fixed-width font (typewriter-like), also known as teletype. (Equivalent CSS: {font-family: monospace;})

TT existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

<u>…</u> (deprecated)

Underlines text. (Equivalent CSS: {text-decoration: underline})

U existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; deprecated in HTML 4.0 Transitional; invalid in HTML 4.0 Strict.

<font>…</font> (deprecated)

<font [color=color] [size=size] [face=face]>…</font>

Can specify the font color with the color attribute, typeface with the face attribute, and absolute or relative size with the size attribute.

Examples (all uses are deprecated, use CSS equivalents if possible):

1. <font color="green">text</font> creates green text.
2. <font color="#114499">text</font> creates text with hexadecimal color #114499.
3. <font size="4">text</font> creates text with size 4. Sizes are from 1 to 7. The standard size is 3, unless otherwise specified in the <body> or other tags.
4. <font size="+1">text</font> creates text with size 1 bigger than the standard. <font size="-1">text</font> is opposite.
5. <font face="Courier">text</font> makes text with Courier font.

Equivalent CSS for font attributes:

• <font size="N"> corresponds to {font-size: Yunits} (the HTML specification does not define the relationship between size N and unit-size Y, nor does it define a unit).
• <font color="red"> corresponds to {color: red}
• <font face="Courier"> corresponds to {font-family: "Courier"}

Standardised in HTML 3.2; deprecated in HTML 4.0 Transitional; invalid in HTML 4.0 Strict.

Span

<span>…</span>

Main article: Span and div

An inline logical division. A generic element with no semantic meaning used to distinguish a document section, usually for purposes such as presentation or behaviour controlled by stylesheets or DOM calls.

Standardised in HTML 4.0; still current.

Other inline elements

<br>

A forced line-break.

Standardised in HTML 2.0; still current.

<bdo>…</bdo>

Marks an inline section of text in which the reading direction is the opposite from that of the parent element.

Standardised in HTML 4.0; still current.

<cite>…</cite>

A citation. Reference for a quote or statement in the document.

CITE existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

<del>…</del>

Deleted text. Typically rendered as a strikethrough: Deleted text.

Standardised in HTML 4.0; still current.

<ins>…</ins>

Inserted text. Often used to mark up replacement text for <del>'d text. Typically rendered underlined: Inserted text.

Standardised in HTML 4.0; still current.

Note, both <ins> and <del> elements may also be used as block elements: containing other block and inline elements. However, these elements must still remain wholly within their parent element to maintain a well-formed HTML document. For example deleting text from the middle of one paragraph across several other paragraphs and ending in a final paragraph would need to use three separate <del> elements. Two <del> elements would be required as inline element to indicate the deletion of text in the first and last paragraphs, and a third, used as a block element, to indicate the deletion in the intervening paragraphs.

<q>…</q>

An inline quotation (for block level quotation see BLOCKQUOTE). Quote elements may be nested.

<q> should automatically generate quotation marks in conjunction with Stylesheets. Practical concerns due to browser non-compliance may force authors to find work-arounds.

The cite attribute gives the source, and must be a fully qualified URI.

Standardised in HTML 4.0; still current.

Note: Lengthy inline quotations may be displayed as indented blocks (as blockquote) using stylesheets. For example, with a suitable CSS rule associated with q.lengthy:

<q class="lengthy">An inline quotation of significant length (say 25 words, for example) goes here...</q>

<script>...</script>

Places a script in the document. Also usable in the head and in block contexts.

Note: <script> is not itself either a block or inline element; by itself it should not display at all, but it can contain instructions to dynamically generate either both block or inline content.

Standardised in HTML 3.2; still current.

<sub>…</sub> and <sup>…</sup>

Mark _subscript or ^superscript text. (Equivalent CSS: {vertical-align: sub} or {vertical-align: super}.)

Both were proposed in the HTML 3.0 Drafts; Standardised in HTML 3.2; still current.

Images and objects

<applet>…</applet> (deprecated)

Embeds a Java applet in the page. Deprecated in favour of <object>, as it could only be used with Java applets, and had accessibility limitations.

Standardised in HTML 3.2; deprecated in HTML 4.0 Transitional; invalid in HTML 4.0 Strict. As of 2010, still widely used as the implementations of the replacing <object> are not consistent between different browsers.

<area>

Specifies a focusable area in a map.

Standardised in HTML 3.2; still current.

<img>

Used by visual user agents to insert an image in the document. The src attribute specifies the image URL. The required alt attribute provides alternative text in case the image cannot be displayed.^[13] (Though alt is intended as alternative text, Microsoft Internet Explorer renders it as a tooltip if no title is given. Safari and Google Chrome, on the other hand, do not display the alt attribute at all.)^[14] img was proposed by Marc Andreessen and implemented in the NSCA Mosaic web browser.^[15]

IMG existed in HTML Internet Draft 1.2, and was standardised in HTML 2.0; still current.

<map>…</map>

Specifies a client-side image map.

Standardised in HTML 3.2; still current.

<object>…</object>

Includes an object in the page of the type specified by the type attribute. This may be in any MIME-type the user agent understands, such as an embedded HTML page, a file to be handled by a plug-in such as Flash, a Java applet, a sound file, etc.

Standardised in HTML 4.0; still current.

<param>

Originally introduced with applet, this element is now used with, and should only occur as a child of object. It uses attributes to set a parameter for the object, e.g. width, height, font, background colour, etc., depending on the type of object. An object can have multiple params.

Standardised in HTML 3.2; still current.

Forms

Main article: HTML form

These elements can be combined into a form or in some instances used separately as user-interface controls; in the document, they can be simple HTML or used in conjunction with Scripts. HTML markup specifies the elements that make up a form, and the method by which it will be submitted. However, some form of scripts (server-side, client-side, or both) must be used to process the user’s input once it is submitted.

(These elements are either block or inline elements, but are collected here as their use is more restricted than other inline or block elements.)

<form action="url">…</form>

Creates a form. The form element specifies and operates the overall action of a form area, using the required action attribute.

Standardised in HTML 2.0; still current.

<button>…</button>

A generic form button which can contain a range of other elements to create complex buttons.

Standardised in HTML 4.0; still current.

<fieldset>…</fieldset>

A container for adding structure to forms. For example, a series of related controls can be grouped within a fieldset, which can then have a legend added in order to identify their function.

Standardised in HTML 4.0; still current.

<input>

input elements allow a variety of standard form controls to be implemented.

Standardised in HTML 2.0; still current.

Input Types:

type="checkbox"

A checkbox. Can be checked or unchecked.

type="radio"

A radio button. If multiple radio buttons are given the same name, the user will only be able to select one of them from this group.

type="button"

A general-purpose button. The element <button> is preferred if possible (i.e. if the client supports it) as it provides richer possibilities.

type="submit"

A submit button.

type="image"

An image button. The image URL may be specified with the src attribute.

type="reset"

A reset button for resetting the form to default values.

type="text"

A one-line text input field. The size attribute specifies the default width of the input in character-widths. maxlength sets the maximum number of characters the user can enter (which may be greater than size).

type="password"

A variation of text. The difference is that text typed in this field is masked — characters are displayed as an asterisk, a dot or another replacement. It should be noted, however, that the password is still submitted to the server as clear text, so an underlying secure transport layer like HTTPS is needed if confidentiality is a concern.

type="file"

A file select field (for uploading files to a server).

type="hidden"

hidden inputs are not visible in the rendered page, but allow a designer to maintain a copy of data that needs to be submitted to the server as part of the form. This may, for example, be data that this web user entered or selected on a previous form that needs to be processed in conjunction with the current form.

<isindex> (deprecated)

isindex could either appear in the document head or in the body, but only once in a document. Requires a server-side search engine.

In the document body, isindex operated as a primitive HTML search form; this use was replaced by the more advanced HTML forms introduced in the early to mid-1990s.

ISINDEX existed in HTML Tags; standardised in HTML 2.0; deprecated in HTML 4.0 Transitional; invalid in HTML 4.0 Strict.

<label for="id">…</label>

Creates a label for a form input (e.g. radio button). Clicking on the label fires a click on the matching input.

Standardised in HTML 4.0; still current.

<legend>…</legend>

A legend (caption) for a fieldset.

Standardised in HTML 4.0; still current.

<option value="x">

Creates an item in a select list.

Standardised in HTML 2.0; still current.

<optgroup>…</optgroup>

Identifies a group of options in a select list.

Standardised in HTML 4.0; still current.

<select name="xyz">…</select>

Creates a selection list, from which the user can select a single option. May be rendered as a dropdown list.

Standardised in HTML 2.0; still current.

<textarea rows="8">…</textarea>

A multiple-line text area, the size of which is specified by cols (where a col is a one-character width of text) and rows attributes. The content of this element is restricted to plain text, which appears in the text area as default text when the page is loaded.

Standardised in HTML 2.0; still current.

Tables

The format of HTML Tables was proposed in the HTML 3.0 Drafts and the later RFC 1942 HTML Tables. They were inspired on the CALS Table Model. Some elements in these proposals were included in HTML 3.2; the present form of HTML Tables was standardised in HTML 4. (Many of the elements used within tables are neither block nor inline elements.)

<table>…</table>

Identifies a table. Several attributes are possible in HTML Transitional, but most of these are invalid in HTML Strict and can be replaced with stylesheets. The summary attribute is however informally required for accessibility purposes, though its usage is not simple.

Proposed in the HTML 3.0 Drafts; Standardised in HTML 3.2; still current.

<tr>…</tr>

Contains a row of cells in a table.

Proposed in the HTML 3.0 Drafts; Standardised in HTML 3.2; still current.

<th>…</th>

A table header cell; contents are conventionally displayed bold and centered. An aural user agent may use a louder voice for these items.

Proposed in the HTML 3.0 Drafts; Standardised in HTML 3.2; still current.

<td>…</td>

A table data cell.

Proposed in the HTML 3.0 Drafts; Standardised in HTML 3.2; still current.

<colgroup>…</colgroup>

Specifies a column group in a table.

Proposed in HTML Tables; Standardised in HTML 4.0; still current.

<col> or <col/>

Specifies a column in a table.

Proposed in HTML Tables; Standardised in HTML 4.0; still current.

<caption>…</caption>

Specifies a caption for a table.

Proposed in the HTML 3.0 Drafts; Standardised in HTML 3.2; still current.

<thead>…</thead>

Specifies the header part of a table. This section may be repeated by the user agent if the table is split across pages (in printing or other paged media).

Proposed in HTML Tables; Standardised in HTML 4.0; still current.

<tbody>…</tbody>

Specifies a body of data for the table.

Proposed in HTML Tables; Standardised in HTML 4.0; still current.

<tfoot>…</tfoot>

Specifies the footer part of a table. Like <thead>, this section may be repeated by the user agent if the table is split across pages (in printing or other paged media).

Proposed in HTML Tables; Standardised in HTML 4.0; still current.

Frames

"iframe" redirects here. For other uses, see IFrame (disambiguation). Main article: Framing (World Wide Web)

Frames allow a visual HTML Browser window to be split into segments, each of which can show a different document. This allows for lower bandwidth use, as repeating parts of a layout can be used in one frame, while variable content is displayed in another. This comes at a significant usability cost, especially in non-visual user agents. Because of this cost, frames (excluding the iframe element) are only allowed in HTML 4.01 Frameset.

In HTML 4.01, a document may contain a head and a body or a head and a frameset, but not both a body and a frameset. However, iframe can be used in a normal document body.

<frameset>…</frameset>

Contains the frameset. The frames layout is given by comma separated lists in the rows and cols attributes.

Standardised in HTML 4.0 Frameset, obsolete in HTML 5.

<frame> or <frame/>

Delimits a single frame, or region, within the frameset. A separate document linked with the src attribute appears inside.

Standardised in HTML 4.0 Frameset, obsolete in HTML 5.

<noframes>…</noframes>

Contains normal HTML content for user agents that don't support frames.

Standardised in HTML 4.0 Transitional, obsolete in HTML 5.

<iframe>…</iframe>

An inline frame places another HTML document in a frame. Unlike an object element, an inline frame can be the "target" frame for links defined by other elements and it can be selected by the user agent as the focus for printing, viewing its source etc.

The content of the element is used as alternative text to be displayed if the browser does not support iframes.

First introduced by Microsoft Internet Explorer in 1997, standardised in HTML 4.0 Transitional, allowed in HTML 5.

Historic elements

Main article: Comparison of layout engines (Non-standard HTML)

The following elements were part of the early HTML developed by Tim Berners-Lee from 1989–91; they are mentioned in HTML Tags, but deprecated in HTML 2.0 and were never part of HTML standards.

<listing>…</listing> (obsolete)

<plaintext> (obsolete)

<xmp>…</xmp> (obsolete)

These elements were used to show fixed-width text; their use was replaced by pre.

plaintext cannot have an end tag – it terminates the markup and causes the rest of the document to be parsed as if it was plain text.

These existed in HTML Tags; deprecated in HTML 2.0; invalid in HTML 4.0.

<nextid>…</nextid> (obsolete)

This element related to the original NeXT http server, and was not used once the web had spread to other systems.

nextid existed in HTML Tags (described as obsolete); deprecated in HTML 2.0; invalid in HTML 3.2 and later.

Non-standard elements

Main article: Comparison of layout engines (Non-standard HTML)

This section lists some widely-used obsolete elements, which means they are not allowed to be used. They may not be supported in all user agents.

<blink>…</blink> (obsolete)

Causes text to blink. Can be done with CSS where supported: {text-decoration: blink} (This effect may have negative consequences for people with epilepsy^[16].; its use on the public internet should follow the appropriate guidelines.)

<marquee>…</marquee> (obsolete)

Creates scrolling text. Can be done with scripting. (This effect may have negative consequences for people with epilepsy^[16]; its use on the public internet should follow the appropriate guidelines.)

<nobr>…</nobr> (obsolete)

Causes text to not break at end of line. Can be done with CSS: {white-space: nowrap;}

<wbr> or <wbr/> (obsolete)

Adds an optional line break the browser may use if required for wrapping. It performs the same function as zero width space (U+200B).

<noembed>…</noembed> (obsolete)

Specifies alternative content, if the embed cannot be rendered.

Comments

<!-- A Comment -->

A comment can appear anywhere in a document, even before the doctype, but not in other tags. (However, placing comments – or indeed any characters except for whitespace – before the doctype will cause Internet Explorer 6 to use quirks mode for the document). None of its enclosed contents are processed. For compatibility with some pre-1995 browsers, the contents of style and script elements are still sometimes surrounded by comment delimiters.

Comments do not nest: the markup <!--Xbegin<!--Y-->Xend--> will yield the comment Xbegin<!--Y and the text Xend--> after it.

References

1. ^ XHTML 1.0 §4.2
2. ^ XML 1.0 (The ability to produce additional elements is part of the eXtensibility in the acronym.)
3. ^ XML 1.0 §5.1
4. ^ XHTML 1.1 §A
5. ^ HTML 4.01 §14.1
6. ^ Ferraiolo, J. Fujisawa, J, and Jackson, D (editors) (2003-01-14). "Scalable Vector Graphics (SVG) 1.1 Specification, §2.3 Options for using SVG in Web pages". W3C. http://www.w3.org/TR/2003/REC-SVG11-20030114/. Retrieved 2009-03-25.
7. ^ HTML 4.01 §12.3
8. ^ HTML 4.01 §14.3.2
9. ^ HTML 4.01 §18
10. ^ CSS §1.1
11. ^ HTML 4.01
12. ^ HTML 4 for dummies, 5th editon, 2005, By Ed Tittel, Mary C. Burmeister, p. 96.
13. ^ The alt attribute's text cannot be styled with markup; as a result, other methods of alternative text presentation, such as Fahrner Image Replacement, have been devised to accommodate situations in which the coder wishes styled text to be displayed if images are disabled in a user's browser.
14. ^ https://bugs.webkit.org/show_bug.cgi?id=5566
15. ^ http://1997.webhistory.org/www.lists/www-talk.1993q1/0182.html
16. ^ ^{a b} Chisholm, Wendy; Vanderheiden, Gregg; Jacobs, Ian (5 May 1999). "Web Content Accessibility Guidelines 1.0". World Wide Web Consortium. http://www.w3.org/TR/WCAG10/. Retrieved 20 July 2010.

Bibliography

HTML standards

HTML 2.0:

Berners-Lee, T., and Connolly, D. (November 1995). "Hypertext Markup Language - 2.0 (RFC 1866)". IETF. http://tools.ietf.org/html/rfc1866. Retrieved 2009-03-24.

HTML 3.2:

Raggett, D. (1997-01-14). "HTML 3.2 Reference Specification". W3C. http://www.w3.org/TR/REC-html32-19970114. Retrieved 2009-03-27.

HTML 4.01:

Raggett, D., Le Hors, A., and Jacobs, I. (editors) (1999-12-24). "HTML 4.01 Specification". W3C. http://www.w3.org/TR/1999/REC-html401-19991224/. Retrieved 2009-03-24. (HTML 4.01 is the updated form of HTML 4.0.)

XHTML 1.0:

W3C (2000-01-26). "XHTML 1.0: The Extensible HyperText Markup Language (Second Edition)". W3C. http://www.w3.org/TR/2002/REC-xhtml1-20020801. Retrieved 2009-03-24.

XHTML 1.1:

Altheim, M., and McCarron, S. (editors) (2001-05-31). "XHTML 1.1 - Module-based XHTML". W3C. http://www.w3.org/TR/2001/REC-xhtml11-20010531/. Retrieved 2009-03-25.

Other sources

HTML Tags:

Berners-Lee, T. (1992-11-03). "HTML Tags". http://www.w3.org/History/19921103-hypertext/hypertext/WWW/MarkUp/Tags.html. Retrieved 2009-03-28. (Part of the first published description of HTML.)

HTML Internet Draft 1.2:

Berners-Lee, T., and Connolly, D. (June 1993). "Hypertext Markup Language (HTML)" (text). http://www.w3.org/MarkUp/draft-ietf-iiir-html-01.txt. Retrieved 2009-03-28.

HTML 3.0 Drafts:

Raggett, D. (1995-03-24). "HyperText Markup Language Specification Version 3.0 (draft)". http://www.w3.org/MarkUp/html3/CoverPage.html. Retrieved 2009-04-18. (This is the final draft of HTML 3.0, which expired without being developed further.)

HTML Tables:

D. Raggett (May 1996). "HTML Tables". RFC 1942. IETF. http://tools.ietf.org/html/rfc1942. Retrieved 2009-03-22.

XML 1.0:

Bray, T, Paoli, J, Sperberg-McQueen, CM, Maler, E and Yergeau, F (editors) (2008-11-26). "Extensible Markup Language (XML) 1.0 (Fifth Edition)". W3C. http://www.w3.org/TR/2008/REC-xml-20081126/. Retrieved 2009-03-20.

CSS:

Lie, H.W. and Bos, B. (2008-04-11). "Cascading Style Sheets, level 1 (revised 2008-04-11)". W3C. http://www.w3.org/TR/CSS1/. Retrieved 2009-04-05.

External links

• Complete lists of elements and attributes for HTML 4.01

Categories: HTML

Personal tools

• New features
• Log in / create account

Namespaces

• Article
• Discussion

">

Variants

Views

• Read
• Edit
• View history

">

Actions

Search">

Search

Navigation

• Main page
• Contents
• Featured content
• Current events
• Random article

Interaction

• About Wikipedia
• Community portal
• Recent changes
• Contact Wikipedia
• Donate to Wikipedia
• Help

Toolbox

• What links here
• Related changes
• Upload file
• Special pages
• Permanent link
• Cite this page

Print/export

• Create a book
• Download as PDF
• Printable version

Languages

• العربية
• Česky
• Español
• فارسی
• Français
• 한국어
• Interlingua
• Italiano
• Kurdî
• Lietuvių
• Magyar
• 日本語
• Português
• Русский
• ไทย
• Українська
• 中文

• This page was last modified on 30 July 2010 at 15:33.
• Text is available under the Creative Commons Attribution-ShareAlike License ; additional terms may apply. See Terms of Use for details.
  Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
• Contact us

• Privacy policy
• About Wikipedia
• Disclaimers