Skip to content

Conversation

ericwilligers
Copy link

No description provided.

@alancutter
Copy link
Owner

I'd like to see the scripts that produce these. The tests are still changing since many of them don't currently work properly under run_benchmark, they'll need to be regenerated.

We create 5 versions for each CSS animation and transition benchmark:-
- compositor-transform = transform animation on compositor thread
- mainthread-transform = transform animation on main thread
- opacity = opacity animation on compositor thread
- px-height = height animation on main thread
- specific-color = color animation on main thread

For web animations, we create the above 5 versions and 3 more:-
- em-height = height animation responsive to font size
- inherit-height = height animation responsive to parent height
- current-color = color animation responsive to parent color

run-big-benchmarks.py is updated to use the generated versions.

A small number of benchmarks fail, sometimes because we have too many
elements. For example, in one run the following failed:-
- web-animations-staggered-chaining-compositor-transform.html
- css-animations-staggered-chaining-by-inserting-style-element-px-height.html
- css-transitions-simultaneous-by-inserting-style-element-specific-color.html
- css-transitions-staggered-chaining-by-updating-class-px-height.html
- css-animations-staggered-chaining-by-inserting-style-element-specific-color.html
- css-animations-staggered-chaining-by-inserting-style-element-mainthread-transform.html
- css-transitions-simultaneous-by-inserting-style-element-px-height.html
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants