css/css-forms

edit

WPT coverage of the tests of css/css-forms at the revision 5602b0f210e3. The tests link to their results in the browsers on wpt.fyi. The tentative tests (experimental features) and the reftests are listed separately from the stable tests.

GroupPassingTestsDisabledPass rate
Stable69067%
Tentative000–
Reftests617035%
All1226046%

Failure reasons

The tests that do not pass (failing or disabled), by kind of reason. A test with several reasons counts once per kind.

  • TEST BUG: 14

Stable tests

TestResultSubtestsKindDescription
appearance-base-basic.htmlPass12 / 12
appearance-base-cursor.htmlFail0 / 25TEST BUGthe cursors of the controls (default, text, not-allowed, also for a label and an input type=range without base appearance; csswg-drafts#14251) are not in the Basic Appearance User Agent Stylesheet of the specification, which the library applies: the controls inherit cursor: pointer from the body (only Chrome passes)
checkbox-checkmark-animation.htmlPass1 / 1
input-file-base-appearance-computed.htmlFail0 / 1TEST BUGthe test expects a border-radius of 0.5em for ::file-selector-button; the style sheet of the specification gives the buttons and the button-like controls border-radius: 4px
input-text-base-appearance-computed-style.htmlFail0 / 1TEST BUGthe test expects no border-radius, align-items: normal (initial) and user-select: auto for a text field with base appearance; the style sheet of the specification gives it border-radius: 4px and align-items: unsafe center
parsing/checkmark-pseudo-element.htmlPass16 / 16
parsing/picker-icon-pseudo-element.htmlPass16 / 16
parsing/picker-select-pseudo-element.htmlPass20 / 20
radio-checkmark-animation.htmlPass1 / 1

Reftests

TestResultVariantsKindDescription
button-base-appearance-rendering.htmlFail0 / 1TEST BUGthe references draw the controls with base appearance as Chrome does, not with the Basic Appearance User Agent Stylesheet of the specification that the library applies: the buttons, the color well and the text fields have border-radius: 4px in the specification (the references have 0.5em or none, so the corners differ); the track of a progress bar is a content box whose inline-size: 100% overflows the control by its borders; the fill of a meter is currentColor (the references color it by the state of the value, red, orange, green, with pseudo-classes such as :even-less-good); the tests fail in every browser of wpt.fyi but Chrome
checkbox-checkmark-animation-002.htmlPass1 / 1
datetime-stacking-context.htmlPass1 / 1
input-button-base-appearance-rendering.htmlFail0 / 1TEST BUGthe references draw the controls with base appearance as Chrome does, not with the Basic Appearance User Agent Stylesheet of the specification that the library applies: the buttons, the color well and the text fields have border-radius: 4px in the specification (the references have 0.5em or none, so the corners differ); the track of a progress bar is a content box whose inline-size: 100% overflows the control by its borders; the fill of a meter is currentColor (the references color it by the state of the value, red, orange, green, with pseudo-classes such as :even-less-good); the tests fail in every browser of wpt.fyi but Chrome
input-checkbox-base-appearance-rendering.htmlPass1 / 1
input-color-base-appearance-rendering.htmlFail0 / 1TEST BUGthe references draw the controls with base appearance as Chrome does, not with the Basic Appearance User Agent Stylesheet of the specification that the library applies: the buttons, the color well and the text fields have border-radius: 4px in the specification (the references have 0.5em or none, so the corners differ); the track of a progress bar is a content box whose inline-size: 100% overflows the control by its borders; the fill of a meter is currentColor (the references color it by the state of the value, red, orange, green, with pseudo-classes such as :even-less-good); the tests fail in every browser of wpt.fyi but Chrome
input-no-resizer.htmlPass1 / 1
input-number-base-appearance-rendering.tentative.htmlFail0 / 1TEST BUGthe references draw the controls with base appearance as Chrome does, not with the Basic Appearance User Agent Stylesheet of the specification that the library applies: the buttons, the color well and the text fields have border-radius: 4px in the specification (the references have 0.5em or none, so the corners differ); the track of a progress bar is a content box whose inline-size: 100% overflows the control by its borders; the fill of a meter is currentColor (the references color it by the state of the value, red, orange, green, with pseudo-classes such as :even-less-good); the tests fail in every browser of wpt.fyi but Chrome
input-search-base-appearance-rendering.tentative.htmlFail0 / 1TEST BUGthe references draw the controls with base appearance as Chrome does, not with the Basic Appearance User Agent Stylesheet of the specification that the library applies: the buttons, the color well and the text fields have border-radius: 4px in the specification (the references have 0.5em or none, so the corners differ); the track of a progress bar is a content box whose inline-size: 100% overflows the control by its borders; the fill of a meter is currentColor (the references color it by the state of the value, red, orange, green, with pseudo-classes such as :even-less-good); the tests fail in every browser of wpt.fyi but Chrome
input-text-base-appearance-rendering.htmlFail0 / 1TEST BUGthe references draw the controls with base appearance as Chrome does, not with the Basic Appearance User Agent Stylesheet of the specification that the library applies: the buttons, the color well and the text fields have border-radius: 4px in the specification (the references have 0.5em or none, so the corners differ); the track of a progress bar is a content box whose inline-size: 100% overflows the control by its borders; the fill of a meter is currentColor (the references color it by the state of the value, red, orange, green, with pseudo-classes such as :even-less-good); the tests fail in every browser of wpt.fyi but Chrome
meter-base-appearance-custom-style-initial-rendering.tentative.htmlFail0 / 1TEST BUGthe references draw the controls with base appearance as Chrome does, not with the Basic Appearance User Agent Stylesheet of the specification that the library applies: the buttons, the color well and the text fields have border-radius: 4px in the specification (the references have 0.5em or none, so the corners differ); the track of a progress bar is a content box whose inline-size: 100% overflows the control by its borders; the fill of a meter is currentColor (the references color it by the state of the value, red, orange, green, with pseudo-classes such as :even-less-good); the tests fail in every browser of wpt.fyi but Chrome
meter-base-appearance-custom-style-value-dynamic-rendering.tentative.htmlFail0 / 1TEST BUGthe references draw the controls with base appearance as Chrome does, not with the Basic Appearance User Agent Stylesheet of the specification that the library applies: the buttons, the color well and the text fields have border-radius: 4px in the specification (the references have 0.5em or none, so the corners differ); the track of a progress bar is a content box whose inline-size: 100% overflows the control by its borders; the fill of a meter is currentColor (the references color it by the state of the value, red, orange, green, with pseudo-classes such as :even-less-good); the tests fail in every browser of wpt.fyi but Chrome
meter-base-appearance-rendering.tentative.htmlFail0 / 1TEST BUGthe references draw the controls with base appearance as Chrome does, not with the Basic Appearance User Agent Stylesheet of the specification that the library applies: the buttons, the color well and the text fields have border-radius: 4px in the specification (the references have 0.5em or none, so the corners differ); the track of a progress bar is a content box whose inline-size: 100% overflows the control by its borders; the fill of a meter is currentColor (the references color it by the state of the value, red, orange, green, with pseudo-classes such as :even-less-good); the tests fail in every browser of wpt.fyi but Chrome
progress-base-appearance-rendering.tentative.htmlFail0 / 1TEST BUGthe references draw the controls with base appearance as Chrome does, not with the Basic Appearance User Agent Stylesheet of the specification that the library applies: the buttons, the color well and the text fields have border-radius: 4px in the specification (the references have 0.5em or none, so the corners differ); the track of a progress bar is a content box whose inline-size: 100% overflows the control by its borders; the fill of a meter is currentColor (the references color it by the state of the value, red, orange, green, with pseudo-classes such as :even-less-good); the tests fail in every browser of wpt.fyi but Chrome
radio-checkmark-animation-002.htmlPass1 / 1
select-combobox-print.htmlPass1 / 1
textarea-base-appearance-rendering.tentative.htmlFail0 / 1TEST BUGthe references draw the controls with base appearance as Chrome does, not with the Basic Appearance User Agent Stylesheet of the specification that the library applies: the buttons, the color well and the text fields have border-radius: 4px in the specification (the references have 0.5em or none, so the corners differ); the track of a progress bar is a content box whose inline-size: 100% overflows the control by its borders; the fill of a meter is currentColor (the references color it by the state of the value, red, orange, green, with pseudo-classes such as :even-less-good); the tests fail in every browser of wpt.fyi but Chrome