supported correctly.CSS support is required for these tests. If it is not enabled, you will get incorrect results
Your browser is currently not applying CSS (or does not support display:none;). Assuming it supports CSS, it should be applying one of the following media types:
screen
projection
handheld
tv
braille
embossed
speech
tty
The spec says Media types are mutually exclusive in the sense that a user agent can only support one media type
when rendering a document. However, user agents may have different modes which support different media types
. Escape 5
breaks this rule by applying screen and projection media types simultaneously (it never applies handheld, even though it
is supposedly designed for devices). WebTV/MSNTV breaks this rule by applying screen and tv media types simultaneously.
(Note, it also does not allow words to be hidden, but that has nothing to do with media types.) Pocket Internet Explorer
also breaks this rule. It completely ignores inline media declarations, and if specified in a media attribute, it mistakes
screen and handheld for each other, and applies both of them at the same time as each other, even if you tell it to use
only screen media (desktop).
Most browsers will apply print media when printing or print previewing, and screen media normally. Opera takes this a step further, also allowing you to switch to projection media (F11) and handheld media (Shift+F11). It also switches to tv media when used on a TV (home media) appliance, and speech media when the text is spoken (try selecting the text in this section and telling Opera to speak it).
Support for generated content is not available in less advanced (and therefore less useful) browsers. You are using one of these browsers.
CSS 3 uses a double colon syntax for generated content. Virtually all browsers that support generated content will work with this syntax, so browsers that do not support it are not very useful. You are using one of these less useful browsers.
Your browser does not allow generated content to replace element content. Your browser is not superior.
Since your browser does not support display:none; it will give incorrect results.
Your browser does not support media queries. That is not very good. Bah! What do you expect.
In fact, your browser actually applies media queries without actually understanding them, so it applies all rules, even if the rule is not actually relevant. That goes against the fundamental rules of CSS. I am not impressed.
Your browser has failed to recognise any rules after the media query - this is very bad. It is one of the fundamental rules of CSS that if a browser does not understand a declaration, it should ignore it, but continue parsing after it. Your browser has failed to do this.
Since your browser does not support display:none; it will give incorrect results.
Browsers are expected to support (at a minimum) CSS 2 selectors. Browsers that can't are either useless for CSS, or force developers to waste time with tricks and hacks to reproduce this useful behaviour. CSS 3 selectors are nice, but not essential.
| CSS 2 :first-child | NoYes Your browser incorrectly applies this selector without understanding it, against the fundamental rules of CSS |
|---|---|
| CSS 2 > | NoYes Your browser incorrectly applies this selector without understanding it, against the fundamental rules of CSS |
| CSS 2 + | NoYes Your browser incorrectly applies this selector without understanding it, against the fundamental rules of CSS |
| CSS 2 [attr=] | NoYes Your browser incorrectly applies this selector without understanding it, against the fundamental rules of CSS |
| CSS 3 [attr*=] | NoYes Your browser incorrectly applies this selector without understanding it, against the fundamental rules of CSS |
| CSS 3 :last-child | Yes Your browser incorrectly applies this selector without understanding it, against the fundamental rules of CSS No |
One of the more clever things that generated content can do is counters. Automatically counting the number of times a selector is matched. Can your browser do it? If so, you should see the word 'Yes' here:
Since your browser does not support display:none; it will give incorrect results.
Browsers should allow the class attribute to have a space separated list of class names, and the class selector should be able to match any one of these. Your browser does this correctly but fails miserably to use the multiple class selector properly fails completely to handle these.
If your browser supports the advanced box model, you should see a green block below these words:
The advanced box model is supported correctly.
Since your browser does not support display:none; it will give incorrect results.
Forget the usual ones (block/inline/list-item/etc). This is a test of the less common, but very useful ones.
Both halves of this test must be passed (aka 'not failed'):