You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new recursive-descent Parser is now implemented and somewhat stable in its featureset. In order to implement the first language, the CSS Parser has to be written from scratch in order to have a real AST that's not limited by a line-by-line parsing approach.
The problem with CSS's specifications is that they are very unclear in regards to syntax, as they heavily rely on a generic "non-ASCII ident token" which pretty much can be everything, including the 💩 emoji.
This issue tries to keep track of the relevant CSS specifications and their implications (to have a feature list of things that are not yet implemented).
Reasons not to implement Media Queries Level 4 and 5: expressions inside the media-feature(s) can be endlessly chained, which is very likely malicious to some extend. Therefore >=, >, <, <= as operators are not being implemented, and only the and and or syntax will be supported.
@media
@supports
Implement the conditions based on the correct precedence of and, or and only.
only as a keyword has no effect, and is only there to make legacy Browsers ignore the media query.
The new recursive-descent Parser is now implemented and somewhat stable in its featureset. In order to implement the first language, the CSS Parser has to be written from scratch in order to have a real AST that's not limited by a line-by-line parsing approach.
The problem with CSS's specifications is that they are very unclear in regards to syntax, as they heavily rely on a generic "non-ASCII ident token" which pretty much can be everything, including the 💩 emoji.
This issue tries to keep track of the relevant CSS specifications and their implications (to have a feature list of things that are not yet implemented).
Animations Level 1
@keyframes
animation
propertiesMedia Queries Level 3
Reasons not to implement Media Queries Level 4 and 5: expressions inside the media-feature(s) can be endlessly chained, which is very likely malicious to some extend. Therefore
>=
,>
,<
,<=
as operators are not being implemented, and only theand
andor
syntax will be supported.@media
@supports
and
,or
andonly
.only
as a keyword has no effect, and is only there to make legacy Browsers ignore the media query.Conditional Rules Level 3
@media
or@supports
rule and therefore can contain bothstyle-rule
andat-rule
inside them.Values and Units Module Level 4
Numeric Data Types:
integer
data typenumber
data typedimension
valuespercentage
valuesratio
data typeLength Data Type
Other Quantities
Other Data Types
color
data typeimage
data typeposition
data type (2d positioning)Functions
attr()
functionPaged Media Module Level 3
@page
ruleThe text was updated successfully, but these errors were encountered: