A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).

Difference between revisions of "PragmaExtensions"

From WHATWG Wiki
Jump to navigation Jump to search
(New page: This page lists the allowed extension values for the http-equiv="" attribute of the <meta> element in HTML5. Such extensions are limited to previously-registered HTTP headers defined in...)
 
(Added {{Obsolete}})
 
(17 intermediate revisions by 9 users not shown)
Line 1: Line 1:
This page lists the allowed extension values for the http-equiv="" attribute of the &lt;meta> element in HTML5. Such extensions are limited to previously-registered HTTP headers defined in an RFC, that have specific user-agent processing requirements, and that do not affect the HTTP processing model. For more details, [http://www.whatwg.org/specs/web-apps/current-work/#concept-http-equiv-extensions see the specification].
{{Obsolete}}


{| 
This page formerly hosted a registry for [https://html.spec.whatwg.org/multipage/semantics.html#pragma-directives http-equiv pragma directives] for the <code>meta</code> element. As of https://github.com/whatwg/html/commit/72d084b81fa94915518b9cf279afef87d835e88e, that model has been abandoned, and further pragma directives must go through the normal standards process for new features instead.
! Keyword
! Brief description
! Specification
|-  
| ''Example''
| ''Causes the user agent to show examples.''
| ''RFC0000''
|}

Latest revision as of 22:49, 13 December 2017

This document is obsolete.


This page formerly hosted a registry for http-equiv pragma directives for the meta element. As of https://github.com/whatwg/html/commit/72d084b81fa94915518b9cf279afef87d835e88e, that model has been abandoned, and further pragma directives must go through the normal standards process for new features instead.