sebastianz / cssdatascraper Goto Github PK

CSS selectors should be added to the output including a group and their syntax.

The information from https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_special_properties should be included in the data structure.

The {{cssappliestoshorthand}} macro is not handled.

It should be interpreted as array of animatable longhands.

See border-image as an example.

If there's a bracket within a syntax defintion, the {{csssyntaxdef}} macro is not parsed correctly.

See the syntax for font-variant as example.

The HTML formatting used in the descriptions for some properties should be kept instead of only reading the plain text.

An example for this is the initial value of text-align.

See also bug 1198959.

The {{csscomputedcolordef}} macro is currently not recognized.

It should be interpreted to reference to the value specified for the color property.

See border-bottom-color as an example.

The {{csspercentagedef}} macro is not handled.

Its first parameter should be set as percentage information.

See transform-origin as an example.

Animated values not wrapped in a macro like the one for all are not scraped.

The {{cssanimatableshorthand}} macro is not handled.

It should be interpreted as array of animatable longhands.

See mask as an example.

Shorthands like background use the csspercentageshorthand macro, which is currently not recognized.

The longhands defined as second parameter of that macro should be read and added as array to the percentages property.

Every group should be prefixed by 'CSS '.

Percentages defined via the {{csspercentagestartdef()}} and {{csspercentageenddef()}}macros should be saved in a property calledpercentages. Instead they are saved in a propertypercentage`.

See max-height for an example.

Sebastian

The {{cssinitialdef}} macro surrounds the value by <code> tags. This formatting should be saved within the scraper output.

Sebastian

The non-terminal-cont value as third parameter of the {{csssyntaxdef}} macro is not recognized.

It should be parsed the same as the non-terminal value.

When the {{cssanimatabledef}} macro is called with only one parameter, it is incorrectly parsed as no.

When the {{cssanimatabledef}} macro is called with three parameters, the third one is incorrectly added to the 'animatable' property value.

See background-size as example.

The {{cssorder}} macro is not handled.

See flex-basis as an example.

Sebastian

The JSON structure created by the scraper should follow the rules outlined in bug 1198949 comment 11. That is:

• remove 'shorthand' (will be determined by one of the other properties being an array)
• remove 'longhands' (other properties will hold arrays of longhands instead)
• 'computed' and 'order' are always set, a keyword (like 'asSpecified' resp. 'uniqueOrder') will be used for 'as specified' resp. 'unique order' values
• 'media', 'animatable', 'percentages', 'initial', 'appliesto', 'computed' and 'order' take either (a) keyword(s), an object of translated strings or an array of longhands in case of a shorthand
• replace common translations like 'all elements' or 'visual' by keywords

Sebastian