
with an Origin HTTP header) is performed along with a credential sent (i.e. If the server does not give credentials to the origin site (by not setting the Access-Control-Allow-Origin HTTP header) the resource will be tainted and its usage restricted.Ī cross-origin request (i.e. no cookie, X.509 certificate, or HTTP Basic authentication). with an Origin HTTP header) is performed, but no credential is sent (i.e. This enumerated attribute indicates whether CORS must be used when fetching the resource.ĬORS-enabled images can be reused in the element without being tainted.Ī cross-origin request (i.e. Srcset or imageset attributes, SVG elements, WebTV supports the use of the value next for rel to preload the next page in a document series.Under XHTML 1.0, void elements such as require a trailing slash.The HTML and XHTML specifications define event handlers for the element, but it is unclear how they would be used.If you encounter problems with the favicon not loading, verify that the Content-Security-Policy header's img-src directive is not preventing access to it. When using to establish a favicon for a site, and your site uses a Content Security Policy (CSP) to enhance its security, the policy applies to the favicon. However, this isn't a good practice to follow it makes more sense to separate your elements from your body content, putting them in the. The crossorigin attribute indicates whether the resource should be fetched with a CORS request.Ī element can occur either in the or element, depending on whether it has a link type that is body-ok.įor example, the stylesheet link type is body-ok, and therefore is permitted in the body. Allowing cross-origin use of images and canvasĪ rel value of preload indicates that the browser should preload this resource (see Preloading content with rel="preload" for more details), with the as attribute indicating the specific class of content being fetched.



