Media Queries allow authors to test and query values or features of the user agent or display device, independent of the document being rendered. They are used in the CSS @media rule to conditionally apply styles to a document, and in various other contexts and languages, such as HTML and Javascript.
Media Queries Level 4 describes the mechanism and syntax of media queries, media types, and media features. It extends and supersedes the features defined in Media Queries Level 3.
CSS is a language for describing the rendering of structured documents
(such as HTML and XML)
on screen, on paper, in speech, etc.
Status of this document
This section describes the status of this document at the time of
its publication. Other documents may supersede this document. A list of
current W3C publications and the latest revision of this technical report
can be found in the W3C technical reports
index at http://www.w3.org/TR/.
This document is a First Public Working Draft.
Publication as a First Public Working Draft does not imply endorsement by the W3C
Membership. This is a draft document and may be updated, replaced or
obsoleted by other documents at any time. It is inappropriate to cite this
document as other than work in progress.
The (archived) public
mailing list www-style@w3.org (see
instructions) is preferred
for discussion of this specification. When sending e-mail, please put the
text “mediaqueries” in the subject, preferably like this:
“[mediaqueries] …summary of comment…”
HTML4 [HTML401] defined a mechanism to support media-dependent style sheets,
tailored for different media types.
For example, a document may use different style sheets for screen and for print.
In HTML, this can be written as:
CSS adapted and extended this functionality with its @media and @import rules,
adding the ability to query the value of individual features:
Inside a CSS style sheet,
one can declare that sections apply to certain media types:
@media screen {
* { font-family: sans-serif }
}
Similarly, stylesheets can be conditionally imported based on media queries:
@import "print-styles.css" print;
Media queries can be used with HTML, XHTML, XML [XMLSTYLE] and the @import and @media rules of CSS.
Here is the same example written in HTML, XHTML, XML, @import and @media:
<link media="screen and (color), projection and (color)"
rel="stylesheet" href="example.css">
<link media="screen and (color), projection and (color)"
rel="stylesheet" href="example.css" />
<?xml-stylesheet media="screen and (color), projection and (color)"
rel="stylesheet" href="example.css" ?>
@import url(example.css) screen and (color), projection and (color);
@media screen and (color), projection and (color) { … }
Note: The [XMLSTYLE] specification has not yet been updated to
use media queries in the media pseudo-attribute.
1.1
Module interactions
This module replaces and extends the Media Queries, Media Type and Media Features
defined in [CSS21] sections 7 and in [MEDIAQ].
1.2
Values
Value types not defined in this specification, such as <integer>,
<number> or <resolution>, are defined in [CSS3VAL]. Other CSS
modules may expand the definitions of these value types.
This specification also introduces some new value types.
The <ratio> value type is a positive (not zero or negative)
<integer> followed by optional whitespace, followed by a solidus ('/'),
followed by optional whitespace, followed by a positive <integer>.
<ratio>s can be ordered or compared by transforming them into the number
obtained by dividing their first <integer> by their second <integer>.
Reasonable to restrict <ratio> to <integer>s?
I’ve seen aspect ratios written with decimal points in real life.
The <mq-boolean> value type is an <integer>
with the value 0 or 1.
Any other integer value is invalid.
Note that -0 is always equivalent to 0 in CSS,
and so is also accepted as a valid <mq-boolean> value.
1.3
Units
The units used in media queries are the same as in other parts of CSS, as
defined in [CSS3VAL]. For example, the pixel unit represents CSS pixels and
not physical pixels.
Relative units in media queries are based on the initial value, which means
that units are never based on results of declarations. For example, in HTML,
the em unit is relative to the initial value of font-size,
defined by the user agent or the user’s preferences,
not any styling on the page.
2
Media Queries
A media query is a method of testing certain aspects of the user agent
or device that the document is being displayed in.
Media queries are (almost) always independent of the contents of the document,
its styling,
or any other internal aspect;
they’re only dependent on “external” information
unless another feature explicitly specifies that it affects the resolution of Media Queries,
such as the @viewport rule.
Statements regarding media queries in this section assume the
syntax section is followed. Media queries that do not
conform to the syntax are discussed in the
error handling section. I.e. the syntax takes
precedence over requirements in this section.
Here is a simple example written in HTML:
<link rel="stylesheet" media="screen and (color)" href="example.css" />
This example expresses that a certain style sheet
(example.css) applies to devices of a certain media type
(screen) with certain feature (it must be a color screen).
Here is the same media query written in an @import-rule in CSS:
@import url(example.css) screen and (color);
User agents should re-evaluate media queries in response to changes in the user environment,
for example if the device is tiled from landscape to portrait orientation,
and change the behavior of any constructs dependent on those media queries accordingly.
Unless another feature explicitly specifies that it affects the resolution of Media Queries, it is never necessary to apply a style sheet in order to evaluate expressions.
Note: CSS Device Adaptation [CSS-DEVICE-ADAPT]]
defines how @viewport rules interact with Media Queries.
2.1
Combining Media Queries
Several media queries can be combined into a comma-separated media query list.
A media query may optionally be prefixed by a single media query modifier,
which is a single keyword which alters the meaning of the following media query.
An individual media query can have its result negated
by prefixing it with the keyword not.
If the media query would normally evaluate to true,
prefixing it with not makes it evaluate to false,
and vice versa.
For example, the following will apply to everything except color-capable screens.
Note that the entire media query is negated,
not just the media type.
<link rel="stylesheet" media="not screen and (color)" href="example.css" />
2.2.2
Hiding a Media Query From Legacy User Agents: the only keyword
The concept of media queries originates from HTML4 [HTML401].
That specification only defined media types,
but had a forward-compatible syntax that accommodated the addition of future concepts like media features:
it would consume the characters of a media query up to the first non-alphanumeric character,
and interpret that as a media type,
ignoring the rest.
For example, the media queryscreen and (color)
would be truncated to just screen.
Unfortunately, this means that legacy user agents using this error-handling behavior
will ignore any media features in a media query,
even if they’re far more important than the media type in the query.
This can result in styles accidentally being applied in inappropriate situations.
To hide these media queries from legacy user agents,
the media query can be prefixed with the keyword only.
The only keyword has no effect on the media query’s result,
but will cause the media query to be parsed by legacy user agents
as specifying the unknown media type “only”,
and thus be ignored.
In this example, the stylesheet specified by the <link> element
will not be used by legacy user agents,
even if they would normally match the screenmedia type.
<link rel="stylesheet" media="only screen and (color)" href="example.css" />
Note: At the time of publishing this specification,
such legacy user agents are extremely rare,
and so using the only modifier is rarely, if ever, necessary.
2.3
Media Types
A media type is a broad category of user-agent devices
on which a document may be displayed.
The original set of media types were defined in HTML4,
for the media attribute on <link> elements.
Unfortunately, media types have proven insufficient as a way of discriminating between devices with different styling needs.
Some categories which were originally quite distinct,
such as screen and handheld,
have blended significantly in the years since their invention.
Others, such as tty or tv,
expose useful differences from the norm of a full-featured computer monitor,
and so are potentially useful to target with different styling,
but the definition of media types as mutually exclusive
makes it difficult to use them in a reasonable manner;
instead, their exclusive aspects are better expressed as media features
such as grid or scan.
Matches printers, and devices intended to reproduce a printed display,
such as a web browser showing a document in “Print Preview”.
screen
Matches all devices that aren’t matched by print or speech.
speech
Matches screenreaders and similar devices that “read out” a page.
In addition, the following deprecatedmedia types are defined.
Authors must not use these media types;
instead, it is recommended that they select appropriate media features
that better represent the aspect of the device that they are attempting to style against.
User agents must recognize the following media types as valid,
but must make them match nothing.
tty
tv
projection
handheld
braille
embossed
aural
Note: It is expected that all of the media types will also be deprecated in time,
as appropriate media features are defined which capture their important differences.
2.4
Media Features
A media feature is a more fine-grained test than media types,
testing a single, specific feature of the user agent or display device.
Syntactically, media features resemble CSS properties:
they consist of a feature name, a colon, and a value to test for.
They may also be written in boolean form as just a feature name,
or in range form with a comparison operator.
There are, however, several important differences between properties and media features:
Properties are used to give information about how to present a document.
Media features are used to describe requirements of the output device.
Media features are always wrapped in parentheses
and combined with the and keyword,
like (color) and (min-width: 600px),
rather than being separated with semicolons.
A media feature may be given with only its name
(omitting the colon and value)
to evaluate the feature in a boolean context.
This is a convenient shorthand for features that have a reasonable value representing 0 or “none”.
For example, (color) is true is the colormedia feature is non-zero.
Properties sometimes accept complex values,
e.g., calculations that involve several other values.
Media features only accept single values: one keyword, one number, etc.
If a media feature does not apply to the device where the UA is running,
that media feature will always be false.
The media feature device-aspect-ratio only applies to
visual devices. On an speech device, expressions involving
device-aspect-ratio will therefore always be false:
<link media="speech and (device-aspect-ratio: 16/9)"
rel="stylesheet" href="example.css">
2.4.1
Media Feature Types: “range” and “discrete”
Every media feature defines its “type” as either “range” or “discrete” in its definition table.
“Discrete” media features,
like light-level or scripting,
take their values from a set.
The values may be keywords
or boolean numbers (0 and 1),
but the common factor is that there’s no intrinsic “order” to them—none of the values are “less than” or “greater than” each other.
“Range” media features like width, on the other hand,
take their values from a range.
Any two values can be compared to see which is lesser and which is greater.
The only significant difference between the two types is that “range” media features
can be evaluated in a range context
and accept “min-” and “max-” prefixes on their name.
Doing either of these changes the meaning of the feature—rather than the media feature being true when the feature exactly matches the given value,
it matches when the feature is greater than/less than/equal to the given value.
A (width >= 600px)media feature is true
when the viewport’s width is 600pxor more.
On the other hand, (width: 600px) by itself is only true
when the viewport’s width is exactly600px.
If it’s less or greater than 600px, it’ll be false.
2.4.2
Evaluating Media Features in a Boolean Context
While media features normally have a syntax similar to CSS properties,
they can also be written more simply as just the feature name,
like (color).
When written like this, the media feature is evaluated in a boolean context.
If the feature would be true for the number 0,
a dimension with the value 0,
or the keyword none,
the media feature evaluates to false.
If it would be true for any values other than the above,
it evaluates to true.
Otherwise, it evaluates to false.
Note: The “trichotomy” above allows for correct handling of MQs as false when on devices where they don’t apply at all,
such as scan on a speech device.
Some media features are designed to be written like this.
For example, scripting is typically written as (scripting) to test if scripting is enabled,
or not (scripting) to see if it’s disabled.
It can still be given an explicit value as well,
with (scripting: enabled) equal to (scripting),
and (scripting: none) equal to not (scripting).
Some numeric media features, like width,
are rarely if ever useful to evaluate in a boolean context,
as their values are almost always greater than zero.
Others, like color, have meaningful zero values:
(color) is identical to (color > 0),
indicating that the device is capable of displaying color at all.
For example, (pointer) is useful,
as pointer has a none value to indicate there’s no pointing device at all on the device.
On the other hand, (scan) is just always true or always false
(depending on whether it applies at all to the device),
as there’s no value that means “false”.
2.4.3
Evaluating Media Features in a Range Context
Media features with a “range” type can be alternately written in a range context
that takes advantage of the fact that their values are ordered,
using ordinary mathematical comparison operators:
The basic form,
consisting of a feature name,
a comparison operator,
and a value,
returns true if the relationship is true.
For example, (height > 600px)
(or (600px < height))
returns true if the viewport height is greater than 600px.
The remaining forms,
with the feature name nested between two value comparisons,
returns true if both comparisons are true.
For example, (400px < width < 1000px) returns true if the viewport width is between 400px and 1000px
(but not equal to either).
2.4.4
Using “min-” and “max-” Prefixes On Range Features
Rather than evaluating a “range” type media feature in a range context,
as described above,
the feature may be written as a normal media feature,
but with a “min-” or “max-” prefix on the feature name.
This is equivalent to evaluating the feature in a range context,
as follows:
Using a “min-” prefix on a feature name is equivalent to using the “>=” operator.
For example, (min-height: 600px) is equivalent to (height >= 600px).
Using a “max-” prefix on a feature name is equivalent to using the “<=” operator.
For example, (max-width: 40em) is equivalent to (width <= 40em).
“Discrete” type properties do not accept “min-” or “max-” prefixes.
Adding such a prefix to a “discrete” type media feature simply results in an unknown feature name.
For example,
(min-grid: 1) is invalid,
because grid is a “discrete” media feature,
and so doesn’t accept the prefixes.
(Even though the gridmedia feature appears to be numeric,
as it accepts the values 0 and 1.)
3
Syntax
Informal descriptions of the media query syntax appear in the prose and railroad diagrams in previous sections.
The formal media query syntax is described in this section,
with the rule/property grammar syntax defined in [CSS3SYN] and [CSS3VAL].
No whitespace is allowed between the "<" or ">" <delim-token>s and the following "=" <delim-token>,
if it’s present.
Whitespace must be present between a ')' character and a not, and, or or keyword,
and between a not, and, or or keyword and a '(' character.
When parsing the <media-in-parens> production,
the <general-enclosed> branch must only be chosen if the input does not match either of the preceding branches.
<general-enclosed> exists to allow for future expansion of the grammar in a reasonably compatible way.
In addition to conforming to the syntax, each media query needs to use
media types and media features according to their respective specification
in order to be considered conforming.
Only the first media query is conforming in the example below because the
"example" media type does not exist.
@media all { body { background:lime } }
@media example { body { background:red } }
Each of the major terms of <media-condition> is associated with a boolean result, as follows:
Authors must not use <general-enclosed> in their stylesheets.
It exists only for future-compatibility,
so that new syntax additions do not invalidate too much of a <media-condition> in older user agents.
The result is the result of evaluating the specified media feature.
3.1
Error Handling
A media query that does not match the grammar in the previous section must be replaced by not all during parsing.
Note: Note that a grammar mismatch does not wipe out an entire media query list,
just the problematic media query.
The parsing behavior defined above automatically recovers at the next top-level comma.
@media (example, all,), speech { /* only applicable to speech devices */ }
@media &test, screen { /* only applicable to screen devices */ }
Both of the above media query lists are turned into not all, speech during parsing,
which has the same truth value as just speech.
An unknown <media-type> must be treated as not matching.
For example, the media query unknown is false,
as unknown is an unknown media type.
But not unknown is true, as the not negates the false media type.
Remember that some keywords aren’t allowed as <media-type>s
and cause parsing to fail entirely:
the media query or and (color) is turned into not all during parsing,
rather than just treating the or as an unknown media type.
<link media="screen and (max-weight: 3kg) and (color), (color)"
rel="stylesheet" href="example.css" />
As max-weight is an unknown media feature,
this media query list is turned into not all, (color),
which is equivalent to just (color).
@media (min-orientation:portrait) { … }
The orientation feature does not accept prefixes,
so this is considered an unknown media feature,
and turned into not all.
The media query (color:20example) specifies an unknown value for the color media feature
and is therefore turned into not all.
This media query is turned into not all because negative lengths are not allowed for the width media feature:
@media (min-width: -100px) { … }
Note that media queries are also subject to the parsing rules of the host language.
For example, take the following CSS snippet:
@media test;,all { body { background:lime } }
The media query test;,all is, parsed by itself,
equivalent to not all, all, which is always true.
However, CSS’s parsing rules cause the @media rule,
and thus the media query,
to end at the semicolon.
The remainder of the text is treated as a style rule
with an invalid selector and contents.
The width media feature describes the width of the targeted display area of the output device.
For continuous media, this is the width of the viewport
(as described by CSS2, section 9.1.1 [CSS21])
including the size of a rendered scroll bar (if any).
For paged media, this is the width of the page box
(as described by CSS2, section 13.2 [CSS21]).
For example, this media query expresses that the style sheet is usable on printed output wider than 25cm:
<link rel="stylesheet" media="print and (min-width: 25cm)" href="http://…" />
This media query expresses that the style sheet is usable on devices with viewport
(the part of the screen/paper where the document is rendered)
widths between 400 and 700 pixels:
@media (min-width: 400px) and (max-width: 700px) { … }
This media query expresses that style sheet is usable if the width of the viewport is greater than 20em.
@media (min-width: 20em) { … }
The em value is relative to the initial value of font-size.
The height media feature describes the height of the targeted display area of the output device.
For continuous media, this is the height of the viewport including the size of a rendered scroll bar (if any).
For paged media, this is the height of the page box.
The orientation media feature is portrait
when the value of the height media feature is greater than or equal to
the value of the width media feature.
Otherwise orientation is landscape.
The following media query tests for “portrait” orientation,
like a phone held upright.
The device-width media feature describes the width of the rendering surface of the output device.
For continuous media, this is the width of the screen.
For paged media, this is the width of the page sheet size.
In the example above, the style sheet will apply only to screens
less than 800px in length.
The px unit is of the logical kind,
as described in the Units section.
Note: If a device can be used in multiple orientations,
such as portrait and landscape,
the device-* media features reflect the current orientation.
We should deprecate the device-* media features.
They don’t do anything useful,
and are mostly just abused as a ghetto "phone versus desktop" media type.
We’ve now defined a number of useful MQs for differentiating devices in useful ways instead.
The device-height media feature describes the height of the rendering surface of the output device.
For continuous media, this is the height of the screen.
For paged media, this is the height of the page sheet size.
In the example above, the style sheet will apply only to screens
taller than 600 vertical pixels.
Note that the definition of the px unit is the same as in other parts of CSS.
The 'device-aspect-ratio media feature is defined as the ratio of
the value of the device-width media feature to
the value of the 'device-height media feature.
For example, if a screen device with square pixels
has 1280 horizontal pixels and 720 vertical pixels
(commonly referred to as "16:9"),
the following media queries will all match the device:
The resolution media feature describes the resolution of the output device,
i.e. the density of the pixels,
taking into account the page zoom
but assuming a pinch zoom of 1.0.
When querying devices with non-square pixels,
in min-resolution queries the least-dense dimension must be compared to the specified value
and in max-resolution queries the most-dense dimensions must be compared instead.
A resolution query that’s not evaluated in a range context never matches a device with non-square pixels.
Figure out how to make the above work properly for </> syntax.
Just translate it over directly?
That prevents you from doing a "less than/greater than" dichotomy without using not.
Hmm.
For printers, this corresponds to the screening resolution
(the resolution for printing dots of arbitrary color).
Printers might have a different resolution for grayscale printing.
Another media feature should probably be added to deal with the type of resolution authors want to know to deal with monochrome printing.
This media query simply detects “high-resolution” screens
(those with a hardware pixel to CSS px ratio of at least 2):
@media (resolution >= 2dppx)
For example, this media query expresses that a style sheet is usable on devices with resolution greater than 300 dots per CSS in:
@media print and (min-resolution: 300dpi) { … }
This media query is equivalent, but uses the CSS cm unit:
The scan media feature describes the scanning process of some output devices.
interlace
CRT and some types of plasma TV screens used “interlaced” rendering,
where video frames alternated between specifying only the “even” lines on the screen
and only the “odd” lines,
exploiting various automatic mental image-correction abilities to produce smooth motion.
This allowed them to simulate a higher FPS broadcast at half the bandwidth cost.
When displaying on interlaced screens,
authors should avoid very fast movement across the screen to avoid “combing”,
and should ensure that details on the screen are wider than 1px to avoid “twitter”.
progressive
A screen using “progressive” rendering displays each screen fully,
and needs no special treatment.
Most modern screens, and all computer screens, use progressive rendering.
For example, the “feet” of letters in serif fonts are very small features that can provoke “twitter” on interlaced devices.
The scan media feature can be used to detect this,
and use an alternative font with less chance of “twitter”:
@media (scan: interlace) { body { font-family: sans-serif; } }
The grid media feature is used to query whether the output device is grid or bitmap.
If the output device is grid-based
(e.g., a "tty" terminal, or a phone display with only one fixed font),
the value will be 1.
Otherwise, the value will be 0.
Here is an example that detects a narrow console screen:
The update-frequency media feature is used to query the ability of the output device
to modify the apearance of content once it has been rendered.
It accepts the following values:
none
Once it has been rendered, the layout can no longer be updated.
Example: documents printed on paper.
slow
The layout may change dynamically according to the usual rules of CSS,
but the output device is not able to render or display changes quickly enough
for them to be percieved as a smooth animation.
Example: E-ink screens or severely under-powered devices.
normal
The layout may change dynamically according to the usual rules of CSS,
and the output device is not unusually constrained in speed,
so regularly-updating things like CSS Animations can be used.
Example: computer screens.
For example, if a page styles its links to only add underlines on hover,
it may want to always display underlines when printed:
The overflow-block media feature describes the behavior of the device
when content overflows the viewport in the block axis.
none
There is no affordance for overflow in the block axis;
any overflowing content is simply not displayed.
Examples: billboards
scroll
Overflowing content in the block axis is exposed by allowing users to scroll to it.
Examples: computer screens
optional-paged
Overflowing content in the block axis is exposed by allowing users to scroll to it,
but page breaks can be manually triggered
(such as via break-inside/etc)
to cause the following content to display on the following page.
Examples: slideshows
paged
Content is broken up into discrete pages;
content that overflows one page in the block axis
is displayed on the following page.
Examples: printers, ebook readers
“Viewport” isn’t the right term here, or in overflow-inline.
The overflow-inline media feature describes the behavior of the device
when content overflows the viewport in the inline axis.
none
There is no affordance for overflow in the inline axis;
any overflowing content is simply not displayed.
scroll
Overflowing content in the inline axis is exposed by allowing users to scroll to it.
Note: There are no known implementations of paged overflow of inline-overflowing content,
and the very concept doesn’t seem to make much sense,
so there is intentionally no paged value for overflow-inline.
For example, these two media queries express that a style sheet applies to all color devices:
@media (color) { … }
@media (min-color: 1) { … }
This media query expresses that a style sheet applies to color devices
with at least 8 bits per color component:
@media (color >= 8) { … }
If different color components are represented by different number of bits,
the smallest number is used.
For instance, if an 8-bit color system
represents the red component with 3 bits, the green component with 3 bits, and the blue component with 2 bits,
the color media feature will have a value of 2.
In a device with indexed colors,
the minimum number of bits per color component in the lookup table is used.
Note: The described functionality is only able to describe color capabilities at a superficial level.
If further functionality is required,
RFC2531 [RFC2531] provides more specific media features which may be supported at a later stage.
The color-index media feature describes the number of entries in the color lookup table of the output device.
If the device does not use a color lookup table, the value is zero.
The monochrome media feature describes the number of bits per pixel in a monochrome frame buffer.
If the device is not a monochrome device,
the output device value will be 0.
The pointer media feature is used to query about the presence and accuracy of a pointing device such as a mouse.
If a device has multiple input mechanisms,
the pointer media feature must reflect the characteristics of the “primary” input mechanism,
as determined by the user agent.
(To query the capabilities of any available input mechanism,
see the any-pointer media feature.)
none
The primary input mechanism of the device does not include a pointing device.
coarse
The primary input mechanism of the device includes a pointing device of limited accuracy.
fine
The primary input mechanism of the device includes an accurate pointing device.
Both coarse and fine indicate the presence of a pointing device,
but differ in accuracy.
A pointing device with which it would be difficult or impossible
to reliably pick one of several small adjacent targets at a zoom factor of 1
would qualify as coarse.
Changing the zoom level does not affect the value of this media feature.
Note: As the UA may provide the user with the ability to zoom,
or as secondary pointing devices may have a different accuracy,
the user may be able to perform accurate clicks even if the value of this media feature is coarse.
This media feature does not indicate that the user will never be able to click accurately,
only that it is inconvenient for them to do so.
Authors are expected to react to a value of coarse
by designing pages that do not rely on accurate clicking to be operated.
Typical examples of devices matching combinations of pointer and hover:
pointer
coarse
fine
hover
none
smartphones, touch screens
stylus-based screens (Cintiq, Wacom, etc)
hover
Nintendo Wii controller, Kinect
mouse, touch pad
For accessibility reasons,
even on devices whose pointing device can be described as fine,
the UA may give a value of coarse or none to this media query,
to indicate that the user has difficulties manipulating the input device accurately or at all.
/* Make radio buttons and check boxes larger if we have an inaccurate pointing device */
@media (pointer:coarse) {
input[type="checkbox"], input[type="radio"] {
min-width:30px;
min-height:40px;
background:transparent;
}
}
The hover media feature is used to query the user’s ability to hover over elements on the page.
If a device has multiple input mechanisms,
the hover media feature must reflect the characteristics of the “primary” input mechanism,
as determined by the user agent.
(To query the capabilities of any available input mechanism,
see the any-hover media feature.)
none
Indicates that the primary pointing system can’t hover,
or there is no pointing system.
on-demand
Indicates that the primary pointing system can hover,
but it requires a significant action on the user’s part.
For example, some devices can’t normally hover,
but will activate hover on a “long press”.
hover
Indicates that the primary pointing system can easily hover over parts of the page.
For example, on a touch screen device that can also be controlled by an optional mouse,
the hovermedia feature should match none,
as the primary interaction mode (touching the screen) can’t hover.
Authors should therefore be careful not to assume that the ':hover' pseudo class
will never match on device where 'hover:none' is true,
but they should design layouts that do not depend on hovering to be fully usable.
For accessibility reasons, even on devices that do support hovering,
the UA may give a value of hover: none to this media query,
to opt into layouts that work well without hovering.
/* Only use a hover-activated drop down menu on devices that can hover. */
@media (hover) {
.menu > li {display:inline-block;}
.menu ul {display:none; position:absolute;}
.menu li:hover ul {display:block; list-style:none; padding:0;}
/* ... */
}
The any-pointer and any-hover media features are identical to the pointer and hover media features,
but they correspond to the union of capabilities of all the input devices available to the user.
More than one of their values can match,
if different input devices have different characteristics.
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:
dim
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.
normal
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.
washed
The device is used in an exceptionally bright environment,
causing the screen to be washed out and difficult to read.
For example: bright daylight.
User agents should set the thresholds between the 3 levels
in a way that takes into account the characteristics of the device.
Even though it is expected that User Agents will adjust the value of this media feature
based on ambient light sensors,
this specification intentionally refrains from defining the 3 levels in terms of a measurement in lux,
for several reasons:
Devices equipped with a light sensor usually adjust the brightness of the screen automatically.
Depending on the level of adjustment,
the thresholds for needing a low contrast or hight contrast content may vary.
Different screen technologies wash out at very different ambient light levels;
e-ink displays remain readable in bright daylight,
while liquid crystal displays do not.
Many embedded light sensors are inaccurately calibrated,
making it difficult to establish useful thresholds valid across devices.
For accessibility purposes, user agents may offer manual controls
allowing the user to switch between the 3 levels of independently of the ambient light level,
as high contrast or low contrast styles may be more suitable for users with visual disabilities.
Using this media feature for accessibility purposes overlaps a lot with the high-contrast media feature proposed by Microsoft.
Can we adjust this so that it covers all use cases for both,
or somehow modify them to work in an orthogonal, rather than overlapping, fashion?
Also, the high-contrast media feature could be extended to also cover inverted colors,
as discussed in http://lists.w3.org/Archives/Public/www-style/2013Oct/0672.html
The scripting media feature is used to query whether scripting languages,
such as JavaScript,
are supported on the current document.
enabled
Indicates that the user agent supports scripting of the page
and that support is active for the current document.
initial-only
Indicates that scripting 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.
none
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.
Some user agents have the ability to turn off scripting support on a per script basis or per domain basis,
allowing some, but not all, scripts to run in a particular document.
The scripting media feature does not allow fine grained detection of which script is allowed to run.
In this scenario, the value of the scripting media feature should be enabled
if scripts originating on the same domain as the document are allowed to run,
and none otherwise.
Note: A future level of CSS may extend this media feature to allow fine-grained detection of which script is allowed to run.
Is there a use-case for distinguishing between "UA doesn’t support scripting" and "scripting is supported, but turned off"?
10
Assorted Issues
We need a media feature (or set of media features) to detect the type of keyboard available.
It should be able to distinguish between full computer keyboards, phone dial pads, tv remotes, or virtual keyboards.
As an attempt at an exhaustive list is likely to fail,
finding atomic features to decompose these into would be preferable,
but these remain to be identified.
always vs in text forms only
just numbers vs free alphanumeric input vs full ime support
work properly vs horrible lag like on a tv remove
How much is actually useful for styling?
Example sets of MQs that would match on different types of devices
When designing documents that use media queries,
the same media query may be used in multiple places,
such as to qualify multiple @import statements.
Repeating the same media query multiple times is an editing hazard;
an author making a change must edit every copy in the same way,
or suffer from difficult-to-find bugs in their CSS.
To help ameliorate this,
this specification defines a method of defining custom media queries,
which are simply-named aliases for longer and more complex media queries.
In this way, a media query used in multiple places can instead be assigned to a custom media query,
which can be used everywhere,
and editing the media query requires touching only one line of code.
A custom media query is defined with the @custom-media rule:
For example, if a responsive site uses a particular breakpoint in several places,
it can alias that with a reasonable name:
@custom-media --narrow-window (max-width: 30em);
@media (--narrow-window) {
/* narrow window styles */
}
@media (--narrow-window) and (script) {
/* special styles for when script is allowed */
}
/* etc */
11.1
Script-based Custom Media Queries
Define a map of names to values for JS.
Values can be either a MediaQueryList object or a boolean,
in which case it’s treated identically to the above,
or can be a number or a string,
in which case it’s treated like a normal MQ,
and can use the normal or range context syntax.
Like:
This specification is the product of the W3C Working Group on
Cascading Style Sheets.
Comments from
Arve Bersvendsen,
Björn Höhrmann,
Chris Lilley,
Christoph Päper,
L. David Baron,
Elika J. Etemad,
François Remy,
Melinda Grant,
Nicholas C. Zakas
Philipp Hoschka,
Rick Byers,
Rijk van Geijtenbeek,
Roger Gimson,
Sigurd Lerstad,
Simon Kissane,
Simon Pieters,
Steven Pemberton,
and Susan Lesch
improved this specification.
Conformance
Document conventions
Conformance requirements are expressed with a combination of
descriptive assertions and RFC 2119 terminology. The key words "MUST",
"MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
"RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this
document are to be interpreted as described in RFC 2119.
However, for readability, these words do not appear in all uppercase
letters in this specification.
All of the text of this specification is normative except sections
explicitly marked as non-normative, examples, and notes. [RFC2119]
Examples in this specification are introduced with the words "for example"
or are set apart from the normative text with class="example",
like this:
This is an example of an informative example.
Informative notes begin with the word "Note" and are set apart from the
normative text with class="note", like this:
Note, this is an informative note.
Conformance classes
Conformance to this specification
is defined for three conformance classes:
A style sheet is conformant to this specification
if all of its statements that use syntax defined in this module are valid
according to the generic CSS grammar and the individual grammars of each
feature defined in this module.
A renderer is conformant to this specification
if, in addition to interpreting the style sheet as defined by the
appropriate specifications, it supports all the features defined
by this specification by parsing them correctly
and rendering the document accordingly. However, the inability of a
UA to correctly render a document due to limitations of the device
does not make the UA non-conformant. (For example, a UA is not
required to render color on a monochrome monitor.)
An authoring tool is conformant to this specification
if it writes style sheets that are syntactically correct according to the
generic CSS grammar and the individual grammars of each feature in
this module, and meet all other conformance requirements of style sheets
as described in this module.
Partial implementations
So that authors can exploit the forward-compatible parsing rules to
assign fallback values, CSS renderers must
treat as invalid (and ignore
as appropriate) any at-rules, properties, property values, keywords,
and other syntactic constructs for which they have no usable level of
support. In particular, user agents must not selectively
ignore unsupported component values and honor supported values in a single
multi-value property declaration: if any value is considered invalid
(as unsupported values must be), CSS requires that the entire declaration
be ignored.
Experimental implementations
To avoid clashes with future CSS features, the CSS2.1 specification
reserves a prefixed
syntax for proprietary and experimental extensions to CSS.
Prior to a specification reaching the Candidate Recommendation stage
in the W3C process, all implementations of a CSS feature are considered
experimental. The CSS Working Group recommends that implementations
use a vendor-prefixed syntax for such features, including those in
W3C Working Drafts. This avoids incompatibilities with future changes
in the draft.
Non-experimental implementations
Once a specification reaches the Candidate Recommendation stage,
non-experimental implementations are possible, and implementors should
release an unprefixed implementation of any CR-level feature they
can demonstrate to be correctly implemented according to spec.
To establish and maintain the interoperability of CSS across
implementations, the CSS Working Group requests that non-experimental
CSS renderers submit an implementation report (and, if necessary, the
testcases used for that implementation report) to the W3C before
releasing an unprefixed implementation of any CSS features. Testcases
submitted to W3C are subject to review and correction by the CSS
Working Group.
Reasonable to restrict <ratio> to <integer>s?
I’ve seen aspect ratios written with decimal points in real life.
↵
We should deprecate the device-* media features.
They don’t do anything useful,
and are mostly just abused as a ghetto "phone versus desktop" media type.
We’ve now defined a number of useful MQs for differentiating devices in useful ways instead.
↵
Figure out how to make the above work properly for </> syntax.
Just translate it over directly?
That prevents you from doing a "less than/greater than" dichotomy without using not.
Hmm.
↵
Another media feature should probably be added to deal with the type of resolution authors want to know to deal with monochrome printing.
↵
Using this media feature for accessibility purposes overlaps a lot with the high-contrast media feature proposed by Microsoft.
Can we adjust this so that it covers all use cases for both,
or somehow modify them to work in an orthogonal, rather than overlapping, fashion?
Also, the high-contrast media feature could be extended to also cover inverted colors,
as discussed in http://lists.w3.org/Archives/Public/www-style/2013Oct/0672.html
↵
Is there a use-case for distinguishing between "UA doesn’t support scripting" and "scripting is supported, but turned off"?
↵
We need a media feature (or set of media features) to detect the type of keyboard available.
It should be able to distinguish between full computer keyboards, phone dial pads, tv remotes, or virtual keyboards.
As an attempt at an exhaustive list is likely to fail,
finding atomic features to decompose these into would be preferable,
but these remain to be identified.
always vs in text forms only
just numbers vs free alphanumeric input vs full ime support
Define a map of names to values for JS.
Values can be either a MediaQueryList object or a boolean,
in which case it’s treated identically to the above,
or can be a number or a string,
in which case it’s treated like a normal MQ,
and can use the normal or range context syntax.
Like: