Help:HTML in wikitext

Permitted HTML
The following are currently permitted (by default; see Special:Version for additional HTML elements supported by extensions):

The following excerpt from  additionally shows which attributes are allowed. For many HTML elements, more convenient wikitext code is available, see Help:Editing. On the other hand, HTML tags allow an id that can be referenced in one's user style CSS, and allows the tag to be used as link target.

Below from : /**    * Cleans up HTML, removes dangerous tags and attributes, and * removes HTML comments * @private * @param string $text * @param callback $processCallback to do any variable or parameter replacements in HTML attribute values * @param array $args for the processing callback * @return string */   static function removeHTMLtags( $text, $processCallback = null, $args = array, $extratags = array ) { global $wgUseTidy;

static $htmlpairs, $htmlsingle, $htmlsingleonly, $htmlnest, $tabletags, $htmllist, $listtags, $htmlsingleallowed, $htmlelements, $staticInitialised;

wfProfileIn( __METHOD__ );

if ( !$staticInitialised ) {

$htmlpairs = array_merge( $extratags, array( # Tags that must be closed 'b', 'del', 'i', 'ins', 'u', 'font', 'big', 'small', 'sub', 'sup', 'h1', 'h2', 'h3', 'h4', 'h5', 'h6', 'cite', 'code', 'em', 's', 'strike', 'strong', 'tt', 'var', 'div', 'center', 'blockquote', 'ol', 'ul', 'dl', 'table', 'caption', 'pre', 'ruby', 'rt', 'rb' , 'rp', 'p', 'span', 'u'           ) ); $htmlsingle = array(               'br', 'hr', 'li', 'dt', 'dd'            ); $htmlsingleonly = array( # Elements that cannot have close tags               'br', 'hr'            ); $htmlnest = array( # Tags that can be nested--??               'table', 'tr', 'td', 'th', 'div', 'blockquote', 'ol', 'ul',                'dl', 'font', 'big', 'small', 'sub', 'sup', 'span'            ); $tabletags = array( # Can only appear inside table, we will close them               'td', 'th', 'tr',            ); $htmllist = array( # Tags used by list               'ul','ol',            ); $listtags = array( # Tags that can appear in a list               'li',            ); .           .            .        }        .        ..

E.g., element "a" is not allowed, and the wikitext

Main Page

produces the HTML code

&amp;lt;a href="meta.wikimedia.org/wiki/Main_Page"&amp;gt;Main Page&amp;lt;/a&amp;gt;

which renders as the wikitext, not working as a link.

Tags
is a generic inline text container.

is a similar tag which is (should not be used) in favor of   .''

For example produces the same result as

See also &#123;&#123;font size demo&#125;&#125; and  Help:Text color.

It's pointless to combine the legacy tag with inline CSS; legacy browsers would ignore the CSS, while modern browsers support  (see above).

Note that in most cases, one can use a more descriptive tag, for instance,  to indicate an important piece of text, or   (subject to the same things as strong) to indicate an emphasized piece of text.

This not only draws the user's attention to the text, but can also alert those who are using nonvisual browsers or have sight impairments, etc. to the fact that that is emphasized text.

Using as a link target
The standard way of providing a named anchor as an invisible target (i.e. ) doesn't work (since all   tags are converted), and an alternative suggested by the W3C, , produces an "[Edit]" link.

However,  does produce a target than can be the destination of a link. Note that it doesn't work everywhere; for instance, in a table, it has to be inside a cell before some browsers will jump to it properly.

is a generic block container. Rules:
 * should be followed by a newline
 * should be preceded by a newline
 * followed by text on the same line, two newlines and text before  on the same line should be avoided (because the two newlines only produce a space)

Example:

See &lt;div&gt; section of  Help:HTML in wikitext.

HTML comment
See HTML comment section of  Help:HTML in wikitext.

Attributes
Most tags can have a  attribute. For example

produces:  This is red text.

Most tags can have classes and IDs. They can be used in conjunction with stylesheets to give a piece of text a descriptive class (or unique identifier) and to refer to that in a stylesheet. For example



Example tooltip box Produces the box which floats on the left because  class is already defined in local Mediawiki:Common.css. 

Classes and IDs can also be used by Javascript code, for example see how {Link FA} works in enwiki.

Another attribute example is, for example used with a span tag: note the hover box (should say "Who knows what it is?") over "unknown substance"  "some special items require an unknown substance to make"

HTML for "unknown substance"

Pre
tags work as the combination of  and the standard HTML   tag: the content will preformatted, and it will not be parsed, but shown as in the wikitext source. If you want preformatted but parsed text, use a space in the beginning of the line instead. For example,

This word is bold. This word is bold. will render as

This word is bold. This word is bold.

Comments
HTML comments in the wikitext will not appear in the HTML code at all.

Headers
Headers ( ... ) will be treated in a similar way as wikicode headers:

sample header

Note that it appears in the table of contents and has an accompanying edit link. There are some minor differences though: editing such a section won't prefill the edit summary, and the browser won't jump to the beginning of the section when saving the page. Thus, you should use the wikitext equivalents instead.

Exceptions
In some pages in the MediaWiki namespace (typically the short messages like button labels) HTML does not work, and e.g. &lt;span id=abc&gt; produces the HTML &amp;lt;span id=abc&amp;gt; rendered by the browser as &lt;span id=abc&gt;. Some others are interpreted as pure HTML (thus any tag can be used, but wikicode won't be transformed to HTML).

User CSS and JS pages (see Help:User style) are interpreted as if inside a  block. From MW 1.11 this also goes for sitewide CSS/JS; in earlier versions (MW 1.10 and earlier), you have to manually add  to the beginning and   to the end of those pages to avoid strange rendering.