Closed Bug 1189440 Opened 9 years ago Closed 7 years ago

Consider using shepherd (bikeshed tool) in the context of CSSData

Categories

(Developer Documentation Graveyard :: CSS, defect, P5)

Product:
Developer Documentation Graveyard
Component:
CSS
Platform:
All
Other
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: teoli, Unassigned)

Details

:: Developer Documentation Request

      Request Type: New Documentation
     Gecko Version: unspecified
 Technical Contact: 

:: Details

cvrebert pointed out that shepherd, a W3C tool could be useful to replace or help generate CSSData: https://github.com/tabatkins/bikeshed/blob/7416878f12ab111d0df91484a66967129f370bf2/bikeshed/update.py#L31

A priori this is a good idea (it could allow us to have the info before we create a CSS property page and remove the sync need to update CSSData), but we should consider several aspects:
- performance
- can we get all the info needed from it.
- do we need a way to override it (place we diverge from the standard)
- how to deal with pseudo-elements, descriptors, pseudo-classes...

But this is interesting.
CSS data lives in its own repo now. If this is still relevant, please file an issue here https://github.com/mdn/data
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
I think the idea behind that is still very good, so I've filed https://github.com/mdn/data/issues/93.

Sebastian
You need to log in before you can comment on or make changes to this bug.