Don't invalidate parent if it didn't change
authorBenjamin Otte <otte.benjamin@googlemail.com>
Fri, 6 May 2022 11:50:55 +0000 (11:50 +0000)
committerMatthias Clasen <mclasen@redhat.com>
Sat, 7 May 2022 14:31:00 +0000 (10:31 -0400)
commitfc5966a34755f40181f6b9f1f137238773b73950
tree9ca5cdba3cc7ef030da4028e9fa94e07bad6cb1f
parent55a4b4a174ef2bd891cc689df01ba3bb1f76b77d
Don't invalidate parent if it didn't change

This looks like a leftover excess invalidation from when the surrounding
code was refactored to not just be called on parent changes but also
when repositioning inside the same parent in commit
507016cafc407b2c47aea3fd1483df75e9757f29

Ivan Molodetskikh found this problem in
https://gitlab.gnome.org/GNOME/gtk/-/issues/3334#note_1445873 which
contains a longer analysis of this problem and the performance
reductions it causes.

Related: #3334
gtk/gtkcssnode.c