Open
Description
I think we can improve the Use cases section in the following ways:
- The use cases should be labelled according to the desired effect.
ScrollTimeline
is an interface name, not a use case. A use case is something like, "Update navigation to highlight page section". - It would be good to list up the real-world use cases along-side each one. Ultimately we will remove this, but when we present to the CSS WG we should demonstrate that these things really exist. Perhaps just write a "Note:" section listing the URLs.
- The order of the use cases should match the order of the spec, i.e.
a. Triggering use cases
b. Scroll timeline use cases
c. Complex combinations of both - We should illustrate using the CSS syntax (since most readers will be interested in that) followed by the JS-syntax (or the equivalent mapping) unless the use case is one that requires script.
- Also, the code examples don't include the actual animation. We should include that rather than calling
getAnimations[0]
.
- Also, the code examples don't include the actual animation. We should include that rather than calling
- The first use case is unclear: does the heading fade gradually as you scroll? That seems odd. That feels more like a triggering use case.
- In fact, all the use cases seem a bit too abstract. Perhaps we can take a real-world example and just change it a little bit to be less-specific whilst still being real-world.
- The diagrams look good but, if possible, we should draw them using SVG so they can be edited (or alternatively check in the data file for the diagram so someone else can modify it).