MicrosyntaxDescriptions - Revision history

MikeSmith: obsolete this page and direct readers to https://github.com/validator/validator/wiki/Microsyntax-descriptions

2016-12-21T12:00:42Z

obsolete this page and direct readers to https://github.com/validator/validator/wiki/Microsyntax-descriptions

← Older revision		Revision as of 12:00, 21 December 2016
Line 1:		Line 1:
			{{Obsolete\|spec=https://github.com/validator/validator/wiki/Microsyntax-descriptions}}
	The purpose of this page is to enable collaborative creation of brief advisory text for each HTML microsyntax so that when the content of an attribute value or the text content of an element does not conform to a given microsyntax, a validator can display the advisory text about the syntax to guide the author to fix the content. Note that like the rest of this wiki, editing requires you to agree to release your contributions under the MIT license (see wiki footer). Please note that while copying text from the [https://html.spec.whatwg.org/ WHATWG version of HTML] is OK, copying text from RFCs or W3C specs is not OK.		The purpose of this page is to enable collaborative creation of brief advisory text for each HTML microsyntax so that when the content of an attribute value or the text content of an element does not conform to a given microsyntax, a validator can display the advisory text about the syntax to guide the author to fix the content. Note that like the rest of this wiki, editing requires you to agree to release your contributions under the MIT license (see wiki footer). Please note that while copying text from the [https://html.spec.whatwg.org/ WHATWG version of HTML] is OK, copying text from RFCs or W3C specs is not OK.

MikeSmith: /* custom-element-name */ note parsing effects

2016-12-20T11:24:56Z

custom-element-name: note parsing effects

← Older revision		Revision as of 11:24, 20 December 2016
Line 33:		Line 33:

	==custom-element-name==		==custom-element-name==
	A [https://html.spec.whatwg.org/multipage/scripting.html#valid-custom-element-name valid custom element name]. Must contain a hyphen, must begin with a lowercase letter, and must not contain any uppercase letters.		A [https://html.spec.whatwg.org/multipage/scripting.html#valid-custom-element-name valid custom element name]. Must contain a hyphen, must (after parsing) begin with a lowercase ASCII letter, and must (after parsing) not contain any uppercase ASCII letters. (Remember that HTML parsers lowercase element names but don’t lowercase attribute values.)

	==date==		==date==

MikeSmith: added custom-element-name

2016-12-19T11:09:40Z

added custom-element-name

← Older revision		Revision as of 11:09, 19 December 2016
Line 31:		Line 31:
	==content-security-policy==		==content-security-policy==
	A valid [https://developer.mozilla.org/en-US/docs/Web/Security/CSP/Using_Content_Security_Policy#Writing_a_policy Content Security Policy].		A valid [https://developer.mozilla.org/en-US/docs/Web/Security/CSP/Using_Content_Security_Policy#Writing_a_policy Content Security Policy].

			==custom-element-name==
			A [https://html.spec.whatwg.org/multipage/scripting.html#valid-custom-element-name valid custom element name]. Must contain a hyphen, must begin with a lowercase letter, and must not contain any uppercase letters.

	==date==		==date==

MikeSmith: removed date-or-time see https://github.com/validator/validator/issues/404

2016-12-17T14:20:16Z

removed date-or-time see https://github.com/validator/validator/issues/404

← Older revision		Revision as of 14:20, 17 December 2016
Line 34:		Line 34:
	==date==		==date==
	A date in the form <code><i>YYYY</i>-<i>MM</i>-<i>DD</i></code>. Example: <code>2002-09-29</code>.		A date in the form <code><i>YYYY</i>-<i>MM</i>-<i>DD</i></code>. Example: <code>2002-09-29</code>.

	~~==date-or-time==~~
	~~A [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-date-or-time-string date or time string]; that is, one of the following:~~
	a <b>date</b>, which must be in the form <code><i>YYYY</i>-<i>MM</i>-<i>DD</i></code> • or, a <b>time</b>, which must begin in the form <code><i>hh</i>:<i>mm</i></code>, and can optionally be followed by <code>:<i>ss</i></code>, which in turn can optionally be followed by “<code>.</code>” and one or more digits • or, a <b>date</b>, followed by “<code>T</code>”, followed by a <b>time</b>, followed by <b>time-zone information</b>, which must be either “<code>Z</code>”, or in the form <code>+<i>hh</i>:<i>mm</i></code> or the form <code>-<i>hh</i>:<i>mm</i></code> • Examples: <code>1996-01-01</code>, <code>12:05:25</code>, <code>1996-01-01T12:05:25-02:00</code>, <code>1996-01-01T12:05:25.6</code> • <i>Note: The validator currently allows some values that the HTML specification prohibits; for example, it allows <code>1996-01-01T12:05:25</code> (a date and time with no time-zone information) and <code>12:05:25Z</code> (a time with no date but with time-zone information).</i>

	==datetime==		==datetime==

MikeSmith: autofill-any

2016-12-17T13:23:04Z

autofill-any

← Older revision		Revision as of 13:23, 17 December 2016
Line 7:		Line 7:
	==a-rel==		==a-rel==
	A whitespace-separated list of link types, with no duplicate keywords in the list. Each link type must be listed as allowed on <code><a></code> and <code><area></code> in the [https://html.spec.whatwg.org/multipage/semantics.html#linkTypes HTML specification], or must be listed as allowed on <code><a></code> and <code><area></code> on the [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions Microformats wiki]. <strong>You can register link types on the [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions Microformats wiki] yourself.</strong>		A whitespace-separated list of link types, with no duplicate keywords in the list. Each link type must be listed as allowed on <code><a></code> and <code><area></code> in the [https://html.spec.whatwg.org/multipage/semantics.html#linkTypes HTML specification], or must be listed as allowed on <code><a></code> and <code><area></code> on the [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions Microformats wiki]. <strong>You can register link types on the [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions Microformats wiki] yourself.</strong>

			==autocomplete-any==
			A list of [https://html.spec.whatwg.org/multipage/forms.html#autofill-detail-tokens autofill detail tokens].

	==browsing-context==		==browsing-context==

MikeSmith: /* iri-ref-http-or-https */

2016-12-17T12:56:56Z

iri-ref-http-or-https

← Older revision		Revision as of 12:56, 17 December 2016
Line 90:		Line 90:

	==iri-ref-http-or-https==		==iri-ref-http-or-https==
	~~A list of <code>http</code> or <code>https</code>~~ [https://wiki.whatwg.org/wiki/MicrosyntaxDescriptions#iri-ref ~~URLs~~].		Any [https://wiki.whatwg.org/wiki/MicrosyntaxDescriptions#iri-ref URL] whose scheme is <code>http</code> or <code>https</code>.

	==language==		==language==

MikeSmith: update ping datatype

2016-12-17T12:51:22Z

update ping datatype

← Older revision		Revision as of 12:51, 17 December 2016
Line 88:		Line 88:
	==iri-ref==		==iri-ref==
	Any URL. For example: <code>/hello</code>, <code>#canvas</code>, or <code><nowiki>http://</nowiki>example.org/</code>. Characters should be represented in [http://www.macchiato.com/unicode/nfc-faq NFC] and spaces should be escaped as <code>%20</code>. Common non-alphanumeric characters other than <code>! $ & ' ( ) * + - . / : ; = ? @ _ ~</code> generally must be [https://en.wikipedia.org/wiki/Percent-encoding percent-encoded]. For example, the pipe character (<code>\|</code>) must be encoded as <code>%7C</code>.		Any URL. For example: <code>/hello</code>, <code>#canvas</code>, or <code><nowiki>http://</nowiki>example.org/</code>. Characters should be represented in [http://www.macchiato.com/unicode/nfc-faq NFC] and spaces should be escaped as <code>%20</code>. Common non-alphanumeric characters other than <code>! $ & ' ( ) * + - . / : ; = ? @ _ ~</code> generally must be [https://en.wikipedia.org/wiki/Percent-encoding percent-encoded]. For example, the pipe character (<code>\|</code>) must be encoded as <code>%7C</code>.

			==iri-ref-http-or-https==
			A list of <code>http</code> or <code>https</code> [https://wiki.whatwg.org/wiki/MicrosyntaxDescriptions#iri-ref URLs].

	==language==		==language==

Zcorpan: Fix more links

2016-11-14T10:34:29Z

Fix more links

← Older revision		Revision as of 10:34, 14 November 2016
Line 18:		Line 18:

	==charset==		==charset==
	An preferred encoding name according to the [~~http~~://encoding.spec.whatwg.org/ Encoding Standard]. Example: <code>utf-8</code>		An preferred encoding name according to the [https://encoding.spec.whatwg.org/ Encoding Standard]. Example: <code>utf-8</code>

	==charset-list==		==charset-list==
Line 33:		Line 33:

	==date-or-time==		==date-or-time==
	A [https://html.spec.whatwg.org/multipage/~~common-microsyntaxes~~.html#valid-date-or-time-string date or time string]; that is, one of the following:		A [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-date-or-time-string date or time string]; that is, one of the following:
	a <b>date</b>, which must be in the form <code><i>YYYY</i>-<i>MM</i>-<i>DD</i></code> • or, a <b>time</b>, which must begin in the form <code><i>hh</i>:<i>mm</i></code>, and can optionally be followed by <code>:<i>ss</i></code>, which in turn can optionally be followed by “<code>.</code>” and one or more digits • or, a <b>date</b>, followed by “<code>T</code>”, followed by a <b>time</b>, followed by <b>time-zone information</b>, which must be either “<code>Z</code>”, or in the form <code>+<i>hh</i>:<i>mm</i></code> or the form <code>-<i>hh</i>:<i>mm</i></code> • Examples: <code>1996-01-01</code>, <code>12:05:25</code>, <code>1996-01-01T12:05:25-02:00</code>, <code>1996-01-01T12:05:25.6</code> • <i>Note: The validator currently allows some values that the HTML specification prohibits; for example, it allows <code>1996-01-01T12:05:25</code> (a date and time with no time-zone information) and <code>12:05:25Z</code> (a time with no date but with time-zone information).</i>		a <b>date</b>, which must be in the form <code><i>YYYY</i>-<i>MM</i>-<i>DD</i></code> • or, a <b>time</b>, which must begin in the form <code><i>hh</i>:<i>mm</i></code>, and can optionally be followed by <code>:<i>ss</i></code>, which in turn can optionally be followed by “<code>.</code>” and one or more digits • or, a <b>date</b>, followed by “<code>T</code>”, followed by a <b>time</b>, followed by <b>time-zone information</b>, which must be either “<code>Z</code>”, or in the form <code>+<i>hh</i>:<i>mm</i></code> or the form <code>-<i>hh</i>:<i>mm</i></code> • Examples: <code>1996-01-01</code>, <code>12:05:25</code>, <code>1996-01-01T12:05:25-02:00</code>, <code>1996-01-01T12:05:25.6</code> • <i>Note: The validator currently allows some values that the HTML specification prohibits; for example, it allows <code>1996-01-01T12:05:25</code> (a date and time with no time-zone information) and <code>12:05:25Z</code> (a time with no date but with time-zone information).</i>

Line 43:		Line 43:

	==datetime-tz==		==datetime-tz==
	A [https://html.spec.whatwg.org/multipage/~~common-microsyntaxes~~.html#valid-global-date-and-time-string global date and time string]; that is, a <b>date</b>, followed by a “<code>T</code>” or a single space, followed by a <b>time</b>, followed by <b>time-zone information</b>, where: the <b>date</b> must be in the form <code><i>YYYY</i>-<i>MM</i>-<i>DD</i></code> • the <b>time</b> must begin in the form <code><i>hh</i>:<i>mm</i></code>, followed by <code>:<i>ss</i></code>, optionally followed by “<code>.</code>” and one, two, or three or digits • the <b>time-zone information</b> must be either “<code>Z</code>” or in the form <code>+<i>hh</i>:<i>mm</i></code> or the form <code>-<i>hh</i>:<i>mm</i></code> • Examples: <code>1996-01-01T12:05:25-02:00</code>, <code>1996-01-01T12:05:25Z</code>		A [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-global-date-and-time-string global date and time string]; that is, a <b>date</b>, followed by a “<code>T</code>” or a single space, followed by a <b>time</b>, followed by <b>time-zone information</b>, where: the <b>date</b> must be in the form <code><i>YYYY</i>-<i>MM</i>-<i>DD</i></code> • the <b>time</b> must begin in the form <code><i>hh</i>:<i>mm</i></code>, followed by <code>:<i>ss</i></code>, optionally followed by “<code>.</code>” and one, two, or three or digits • the <b>time-zone information</b> must be either “<code>Z</code>” or in the form <code>+<i>hh</i>:<i>mm</i></code> or the form <code>-<i>hh</i>:<i>mm</i></code> • Examples: <code>1996-01-01T12:05:25-02:00</code>, <code>1996-01-01T12:05:25Z</code>
	<!-- • <i>Note: The validator currently prohibits some values that the HTML specification allows; for example, the HTML specification allows <code>1996-01-01T12:05Z</code> (a date and time string with no seconds specified), but the validator prohibits it.</i> -->		<!-- • <i>Note: The validator currently prohibits some values that the HTML specification allows; for example, the HTML specification allows <code>1996-01-01T12:05Z</code> (a date and time string with no seconds specified), but the validator prohibits it.</i> -->
	<!-- (''[http://canvex.lazyilluminati.com/misc/cgi/issues.cgi/folder/microsyntaxes-dates This format deviates from the spec draft.]'') -->		<!-- (''[http://canvex.lazyilluminati.com/misc/cgi/issues.cgi/folder/microsyntaxes-dates This format deviates from the spec draft.]'') -->
Line 93:		Line 93:

	==link-rel==		==link-rel==
	A whitespace-separated list of link types listed as allowed on <code><link></code> in the [https://html.spec.whatwg.org/multipage/~~links~~.html#linkTypes HTML specification] or listed as an allowed on <code><link></code> on the [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions Microformats wiki] without duplicate keywords in the list. <strong>You can register link types on the [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions Microformats wiki] yourself.</strong>		A whitespace-separated list of link types listed as allowed on <code><link></code> in the [https://html.spec.whatwg.org/multipage/semantics.html#linkTypes HTML specification] or listed as an allowed on <code><link></code> on the [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions Microformats wiki] without duplicate keywords in the list. <strong>You can register link types on the [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions Microformats wiki] yourself.</strong>

	==media-query==		==media-query==
Line 132:		Line 132:

	==script==		==script==
	Any text content that does not contain the character sequence "<code><!--</code>" without a later occurrence of the character sequence "<code>--></code>" and that does not contain any occurrence of the string "<code></script</code>" followed by a space character, "<code>></code>", or "<code>/</code>". For further details, see [https://html.spec.whatwg.org/multipage/scripting-1.html#restrictions-for-contents-of-script-elements Restrictions for contents of script elements].		Any text content that does not contain the character sequence "<code><!--</code>" without a later occurrence of the character sequence "<code>--></code>" and that does not contain any occurrence of the string "<code></script</code>" followed by a space character, "<code>></code>", or "<code>/</code>". For further details, see [https://html.spec.whatwg.org/multipage/scripting.html#restrictions-for-contents-of-script-elements Restrictions for contents of script elements].

	==script-documentation==		==script-documentation==
	Zero or more ''code comments'', each of which is either a single-line comment starting with "<code>//</code>" or a multi-line comment starting with "<code>/</code>" and ending with "<code>/</code>". The content must also meet the constraints of the [https://wiki.whatwg.org/wiki/MicrosyntaxDescriptions#script script] microsyntax. For further details, see [https://html.spec.whatwg.org/multipage/scripting-1.html#inline-documentation-for-external-scripts Inline documentation for external scripts].		Zero or more ''code comments'', each of which is either a single-line comment starting with "<code>//</code>" or a multi-line comment starting with "<code>/</code>" and ending with "<code>/</code>". The content must also meet the constraints of the [https://wiki.whatwg.org/wiki/MicrosyntaxDescriptions#script script] microsyntax. For further details, see [https://html.spec.whatwg.org/multipage/scripting.html#inline-documentation-for-external-scripts Inline documentation for external scripts].

	==simple-color==		==simple-color==
Line 153:		Line 153:

	==time-datetime==		==time-datetime==
	One of the following: [https://html.spec.whatwg.org/multipage/~~common-microsyntaxes~~.html#valid-month-string month], [https://html.spec.whatwg.org/multipage/~~common-microsyntaxes~~.html#valid-date-string date], [https://html.spec.whatwg.org/multipage/~~common-microsyntaxes~~.html#valid-yearless-date-string yearless date], [https://html.spec.whatwg.org/multipage/~~common-microsyntaxes~~.html#valid-time-string time], [https://html.spec.whatwg.org/multipage/~~common-microsyntaxes~~.html#valid-local-date-and-time-string local date and time], [https://html.spec.whatwg.org/multipage/~~common-microsyntaxes~~.html#valid-time-zone-offset-string time-zone offset], [https://html.spec.whatwg.org/multipage/~~common-microsyntaxes~~.html#valid-global-date-and-time-string global date and time], [https://html.spec.whatwg.org/multipage/~~common-microsyntaxes~~.html#valid-week-string week], [https://html.spec.whatwg.org/multipage/~~common-microsyntaxes~~.html#valid-non-negative-integer non-negative integer], or [https://html.spec.whatwg.org/multipage/~~common-microsyntaxes~~.html#valid-duration-string duration]. For more information and examples, see the [https://html.spec.whatwg.org/multipage/~~text-level-~~semantics.html#datetime-value section on the datetime value in the HTML specification].		One of the following: [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-month-string month], [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-date-string date], [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-yearless-date-string yearless date], [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-time-string time], [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-local-date-and-time-string local date and time], [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-time-zone-offset-string time-zone offset], [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-global-date-and-time-string global date and time], [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-week-string week], [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-non-negative-integer non-negative integer], or [https://html.spec.whatwg.org/multipage/infrastructure.html#valid-duration-string duration]. For more information and examples, see the [https://html.spec.whatwg.org/multipage/semantics.html#datetime-value section on the datetime value in the HTML specification].

	==week==		==week==

Zcorpan: /* a-rel */ Fix link

2016-11-14T10:19:49Z

a-rel: Fix link

← Older revision		Revision as of 10:19, 14 November 2016
Line 6:		Line 6:

	==a-rel==		==a-rel==
	A whitespace-separated list of link types, with no duplicate keywords in the list. Each link type must be listed as allowed on <code><a></code> and <code><area></code> in the [https://html.spec.whatwg.org/multipage/~~links~~.html#linkTypes HTML specification], or must be listed as allowed on <code><a></code> and <code><area></code> on the [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions Microformats wiki]. <strong>You can register link types on the [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions Microformats wiki] yourself.</strong>		A whitespace-separated list of link types, with no duplicate keywords in the list. Each link type must be listed as allowed on <code><a></code> and <code><area></code> in the [https://html.spec.whatwg.org/multipage/semantics.html#linkTypes HTML specification], or must be listed as allowed on <code><a></code> and <code><area></code> on the [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions Microformats wiki]. <strong>You can register link types on the [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions Microformats wiki] yourself.</strong>

	==browsing-context==		==browsing-context==

MikeSmith: /* media-query */ make the media-type part of a media query optional

2016-07-30T23:44:04Z

media-query: make the media-type part of a media query optional

← Older revision		Revision as of 23:44, 30 July 2016
Line 96:		Line 96:

	==media-query==		==media-query==
	One or more media queries, combined in a comma-separated list. Each media query consists of a <strong>media type</strong> and zero or more expressions that check for the conditions of particular <strong>media features</strong>. A media type is one of the following: <code>all</code>, <code>print</code>, <code>screen</code>, or <code>speech</code>. The following media types are deprecated: <code>braille</code>, <code>embossed</code>, <code>handheld</code>, <code>projection</code>, <code>tty</code>, and <code>tv</code>. For information about valid media features and about the exact syntax of media queries, see the [https://drafts.csswg.org/mediaqueries/ Media Queries] specification.		One or more media queries, combined in a comma-separated list. Each media query consists of a optional <strong>media type</strong> and zero or more expressions that check for the conditions of particular <strong>media features</strong>. A media type is one of the following: <code>all</code>, <code>print</code>, <code>screen</code>, or <code>speech</code>. The following media types are deprecated: <code>braille</code>, <code>embossed</code>, <code>handheld</code>, <code>projection</code>, <code>tty</code>, and <code>tv</code>. For information about valid media features and about the exact syntax of media queries, see the [https://drafts.csswg.org/mediaqueries/ Media Queries] specification.

	==meta-charset==		==meta-charset==