﻿<?xml version="1.0" encoding="utf-8"?>
<!--
Media Queries Level 5
Editor�s Draft, 21 May 2019
https://drafts.csswg.org/mediaqueries-5/
-->
<definitions xmlns="urn:schemas-jetbrains-com:css-xml">
  <media-feature id="environment-blending" declared-in="5.0" url="https://drafts.csswg.org/mediaqueries-5/#descdef-media-environment-blending" min-max="no">
    <description>
      <![CDATA[<p>The environment-blending media feature is used to query the characteristics of the user�s display so the author can adjust the style of the document. An author might choose to adjust the visuals and/or layout of the page depending on the display technology to increase the appeal or improve legibility.</p>]]></description>
    <group type="or">
      <name value="opaque"
            tooltip="The document is rendered on an opaque medium, such as a traditional monitor or paper. Black is dark and white is 100% light." />
      <name value="additive"
            tooltip="The display blends the colors of the canvas with the real world using additive mixing. Black is fully transparent and white is 100% light. For example: a head-up display in a car." />
      <name value="subtractive"
            tooltip="The display blends the colors of the canvas with the real world using subtractive mixing. White is fully transparent and dark colors have the most contrast. For example: an LCD display embedded in a bathroom mirror." />
    </group>
  </media-feature>

  <media-feature id="forced-colors" declared-in="5.0" url="https://drafts.csswg.org/mediaqueries-5/#descdef-media-forced-colors" min-max="no">
    <description>
      <![CDATA[<p>The forced-colors media feature is used to detect if the user agent has enabled a forced colors mode where it enforces a user-chosen limited color palette on the page.</p>]]></description>
    <group type="or">
      <name value="none" tooltip="Forced colors mode is not active; the page�s colors are not being forced into a limited palette." />
      <name value="active"
            tooltip="Indicates that forced colors mode is active. The UA will provide the color palette to authors through the CSS system color keywords and, if appropriate, trigger the appropriate value of prefers-color-scheme so that authors can adapt the page. See [[!css-color-adjust-1#forced]] for details." />
    </group>
  </media-feature>

  <media-feature id="inverted-colors" declared-in="5.0" url="https://drafts.csswg.org/mediaqueries-5/#descdef-media-inverted-colors" min-max="no">
    <description>
      <![CDATA[<p>The inverted-colors media feature indicates whether the content is displayed normally, or whether colors have been inverted.</p>]]></description>
    <group type="or">
      <name value="none" tooltip="Colors are displayed normally." />
      <name value="inverted"
            tooltip="All pixels within the displayed area have been inverted. This value must not match if the User Agent has done some kind of content aware inversion such as one that preserves the images. Note: This is because the goal of this media feature is to enable authors to mitigate the undesirable effects of the non content aware approach that invert all the pixels. If the author were to take counter measures even in the content-aware cases, their counter measures and the UA�s would be at risk of cancelling each other." />
    </group>
  </media-feature>

  <media-feature id="light-level" declared-in="5.0" url="https://drafts.csswg.org/mediaqueries-5/#descdef-media-light-level" min-max="no">
    <description>
      <![CDATA[<p>The light-level media feature is used to query about the ambient light-level in which the device is used, to allow the author to adjust style of the document in response. The following values are valid:</p>]]></description>
    <group type="or">
      <name value="dim"
            tooltip="The device is used in a dim environment, where excessive contrast and brightness would be distracting or uncomfortable to the reader. For example: night time, or a dimly illuminated indoor environment." />
      <name value="normal"
            tooltip="The device is used in a environment with a light level in the ideal range for the screen, and which does not necessitate any particular adjustment." />
      <name value="washed"
            tooltip="The device is used in an exceptionally bright environment, causing the screen to be washed out and difficult to read. For example: bright daylight." />
    </group>
  </media-feature>

  <media-feature id="prefers-color-scheme" declared-in="5.0" url="https://drafts.csswg.org/mediaqueries-5/#descdef-media-prefers-color-scheme" min-max="no">
    <description>
      <![CDATA[<p>The prefers-color-scheme media feature is used to detect if the user has requested the page use a light or dark color theme.</p>]]></description>
    <group type="or">
      <name value="no-preference"
            tooltip="Indicates that the user has made no preference known to the system. This keyword value evaluates as false in the boolean context." />
      <name value="light"
            tooltip="Indicates that user has notified the system that they prefer a page that has a light theme (dark text on light background)." />
      <name value="dark"
            tooltip="Indicates that user has notified the system that they prefer a page that has a dark theme (light text on dark background)." />
    </group>
  </media-feature>

  <media-feature id="prefers-contrast" declared-in="5.0" url="https://drafts.csswg.org/mediaqueries-5/#descdef-media-prefers-contrast" min-max="no">
    <description>
      <![CDATA[<p>The prefers-contrast media feature is used to detect if the user has requested the system increase or decrease the amount of contrast between adjacent colors. For example, many users have difficulty reading text that has a small difference in contrast to the text background and would prefer a larger contrast.</p>]]></description>
    <group type="or">
      <name value="no-preference"
            tooltip="Indicates that the user has made no preference known to the system. This keyword value evaluates as false in the boolean context." />
      <name value="high"
            tooltip="Indicates that user has notified the system that they prefer an interface that has a higher level of contrast." />
      <name value="low"
            tooltip="Indicates that user has notified the system that they prefer an interface that has a lower level of contrast." />
    </group>
  </media-feature>

  <media-feature id="prefers-reduced-motion" declared-in="5.0" url="https://drafts.csswg.org/mediaqueries-5/#descdef-media-prefers-reduced-motion" min-max="no">
    <description>
      <![CDATA[<p>The prefers-reduced-motion media feature is used to detect if the user has requested the system minimize the amount of animation or motion it uses.</p>]]></description>
    <group type="or">
      <name value="no-preference"
            tooltip="Indicates that the user has made no preference known to the system. This keyword value evaluates as false in the boolean context." />
      <name value="reduce"
            tooltip="Indicates that user has notified the system that they prefer an interface that minimizes the amount of movement or animation, preferably to the point where all non-essential movement is removed." />
    </group>
  </media-feature>

  <media-feature id="prefers-reduced-transparency" declared-in="5.0" url="https://drafts.csswg.org/mediaqueries-5/#descdef-media-prefers-reduced-transparency" min-max="no">
    <description>
      <![CDATA[<p>The prefers-reduced-transparency media feature is used to detect if the user has requested the system minimize the amount of transparent or translucent layer effects it uses.</p>]]></description>
    <group type="or">
      <name value="no-preference"
            tooltip="Indicates that the user has made no preference known to the system. This keyword value evaluates as false in the boolean context." />
      <name value="reduce"
            tooltip="Indicates that user has notified the system that they prefer an interface that minimizes the amount of transparent or translucent layer effects." />
    </group>
  </media-feature>

  <media-feature id="scripting" declared-in="5.0" url="https://drafts.csswg.org/mediaqueries-5/#descdef-media-scripting" min-max="no">
    <description>
      <![CDATA[<p>The scripting media feature is used to query whether scripting languages, such as JavaScript, are supported on the current document.</p>]]></description>
    <group type="or">
      <name value="none"
            tooltip="Indicates that the user agent will not run scripts for this document; either it doesn�t support a scripting language, or the support isn�t active for the current document." />
      <name value="initial-only"
            tooltip="Indicates that the user agent supports scripting of the page, and that scripting in the current document is enabled during the initial page load, but is not supported afterwards. Examples are printed pages, or pre-rendering network proxies that render a page on a server and send a nearly-static version of the page to the user. Should there be an explicit minimum threshold to meet before a UA is allowed to claim initial-only? Having one would mean authors would know what they can depend on, and could tailor their scripts accordingly. On the other hand, pinpointing that threshold is difficult: if it is set too low, the scripting facilities that authors can depend on may be to constrained to be practical, even though actual UAs may potentially all support significantly more. But trying to set it higher may cause us to exclude UAs that do support scripting at loading time, but restrict it in some cases based on complex heuristics. For instance, conservative definitions likely include at least running all inline scripts and firing the DOMContentLoaded event. But it does not seem useful for authors to constrain themselves to this if most (or maybe all) initial-only UAs also load external scripts (including async and defer) and fire the load event. On the other hand, requiring external scripts to be loaded and the load event to be fired could exclude UAs like Opera mini, which typically do run them, but may decide not to based on timeouts and other heuristics. &lt;https://github.com/w3c/csswg-drafts/issues/503&gt;" />
      <name value="enabled"
            tooltip="Indicates that the user agent supports scripting of the page, and that scripting in the current document is enabled for the lifetime of the document." />
    </group>
  </media-feature>

</definitions>