CSS unsupported features on module landing pages

[estelle]

Problem statement

Clarify when a featues is unsuppored in module landing pages

Proposed solutions

Ensure features are listed as "unsupported in any browser" in paragraph format and NOT in list of features format

Task list

• :blank css.selectors.blank
• :current css.selectors.current
• :local-link css.selectors.local-link
• :target-within css.selectors.target-within
• @color-profile css.at-rules.color-profile
• @font-feature-values/font-display css.at-rules.font-feature-values.font-display
• @media/aural css.at-rules.media.aural
• @media/scan css.at-rules.media.scan
• @media/shape css.at-rules.media.shape
• color_value/device-cmyk css.types.color.device-cmyk
• frequency css.types.frequency
• frequency-percentage css.types.frequency-percentage
• image/image css.types.image.image
• image-resolution css.properties.image-resolution
• mask-border-mode

Priority assessment

• Effort:
• Dependencies:
• Community enablement:
• Momentum:
• Enabling learners:
• Enabling professionals:
• Underrepresented topics / Ethical web:
• Operational necessities:
• Addressing needs of the web industry:

More information

Open Web Docs (OWD) is a non-profit collective funded by corporate and individual donations.

In order for this project to happen, please consider donating to OWD at https://opencollective.com/open-web-docs.
For more information on sponsorship and membership tiers, see https://openwebdocs.org/membership/

More information is available at https://openwebdocs.org/.
For questions, please reach out to florian@openwebdocs.org.