Images 💾⌗

Last commit ⭐⌗ 

commit 7bf0f0e908574af28df61ac71925166daef4fc8a
Author:     Andreas Kling <andreas@ladybird.org>
AuthorDate: Mon Sep 9 11:18:32 2024 +0200
Commit:     Nico Weber <thakis@chromium.org>
CommitDate: Wed Oct 30 22:17:22 2024 -0400

    LibWeb: Include immediate child (>) combinator in ancestor filter
    
    Before this change, the ancestor filter would only reject rules that
    required a certain set of descendant strings (class, ID or tag name)
    to be present in the current element's ancestor chain.
    
    An immediate child is also a descendant, so we can include this
    relationship in the ancestor filter as well.
    
    This substantially improves the efficiency of the ancestor filter on
    websites using Tailwind CSS.
    
    For example, https://tailwindcss.com/ itself goes from full style
    updates taking ~1400ms to ~350ms. Still *way* too long, but a huge
    improvement nonetheless.
    
    (cherry picked from commit 34fdd0d44fcf916540ea66ba9c895ba005a54b9a)