Skip to content

Instantly share code, notes, and snippets.

@dzuk-mutant

dzuk-mutant/properties.md

Forked from brianvanburken/properties.md
Last active February 11, 2024 16:05
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save dzuk-mutant/89bd30b02fedf270ebff720527a0f936 to your computer and use it in GitHub Desktop.
Save dzuk-mutant/89bd30b02fedf270ebff720527a0f936 to your computer and use it in GitHub Desktop.
Download ZIP
Feature completeness of my elm-css fork
Raw
properties.md

This is a document covering the completeness of my elm-css fork against most CSS properties and values that currently exist. (This list was compiled by someone else several years ago, so there may be some things missing.)

Source: https://developer.mozilla.org/en-US/docs/Web/CSS/Reference

  • Tick: This has been fully implemented.
  • 🐲: There are tests fully covering this property.
    • (for values this means there is extensive testing for them in property tests)

Selectors

Pseudo-classes

Pseudo-classes with arguments

Pseudo-elements

Pseudo-elements with arguments

Data Types

Other

CSS Grid

At-rules

@media

  • @media implemented as Media.withMedia and Media.withMediaQuery

Media types

  • 🐲 all
  • 🐲 print
  • 🐲 screen

Logical operators

  • 🐲 not
  • 🐲 only

Media queries

Properties

Standard properties and values only. If a property or value is experimental, it should not be a todo.

Removed in my fork

  • textStroke and derivatives. It's an experimental property only used in WebKit.
  • zoom - it's experimental and has no standardisation track.
  • textDecorationSkip - experimental.

Questions

  • Should we create a type for ident that confirms to the specification?
  • Should we add <named-color>?
  • Why is there a transparend : Supported value but no definition?
  • box-shadow support none and elm-css doesn't have this implemented?
  • Should revert be added to everything where unset is allowed?
  • Properties that take in List-based arguments are inconsistent. Some are <property>List and others are <property>s. Which convention should we go for?
    • I'm personally siding with <property>List because its much more visually obvious.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment