commit | 644a01d38fa87f6add2186b951c5c9b4e57d2fdf | [log] [tgz] |
---|---|---|
author | Byungwoo Lee <blee@igalia.com> | Wed Jan 17 08:48:03 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 17 08:48:03 2024 |
tree | c512b8102bc55e6ce65ff25524c2c7ad0b35286a | |
parent | 7b34cef5621acb863d3fdac0dd2276824bc75444 [diff] |
Fix :has() invalidation error with nesting parent containing hover Sets ContainsPseudoInsideHasPseudoClass flag of a :has() selector if its argument contains nesting parent. Currently, the CSSSelectorParser doesn't set the above flag if the :has() selector's argument has a nesting parent selector and the nesting parent contains a pseudo selector. Due to this, even if the pseudo state in the nesting parent is changed, StyleEngine skips :has() invalidation for the pseudo state change because the :has() anchor element doesn't have AffectedByPseudoInHas flag set. To fix this, CSSSelectorParser sets ContainsPseudoInsideHasPseudoClass flag if the :has() selector contains a nesting parent selector in its argument selector. Bug: 1517866 Change-Id: I41b6f69a83db41a4e519490018bfb214a724f807 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5203146 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Byungwoo Lee <blee@igalia.com> Cr-Commit-Position: refs/heads/main@{#1248019}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.