-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
LibWeb: Fixes to inherited style recomputation & transitions #6837
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
Hello! One or more of the commit messages in this PR do not match the Ladybird code submission policy, please check the |
345c742 to
b076f39
Compare
|
Your pull request has conflicts that need to be resolved before it can be reviewed and merged. Make sure to rebase your branch on top of the latest |
b076f39 to
6d35692
Compare
|
Rebased to resolve conflicts |
|
Your pull request has conflicts that need to be resolved before it can be reviewed and merged. Make sure to rebase your branch on top of the latest |
Reduces the rebuild required when editing this file
Previously we assumed that if the non-animated value was inherited then the animated value must be also which is not true.
We only need to consider the change in the value that is actually used, not the animated and non-animated values individually
We were missing the important flag here so would always reset it to false
We can achieve the same thing by using `parse_simple_comma_separated_value_list`
CSS transitions have a higher precedence in the cascade than important properties
6d35692 to
c2e6308
Compare
Bit of a messy PR combined into one to avoid merge conflicts, includes:
recompute_inherited_styleSee individual commits for details.