aboutsummaryrefslogtreecommitdiffstats
path: root/components/script/dom/bindings/codegen/parser/tests/test_namespace.py
diff options
context:
space:
mode:
authorJ. Ryan Stinnett <jryans@gmail.com>2017-05-22 15:09:45 -0500
committerJ. Ryan Stinnett <jryans@gmail.com>2017-05-24 18:08:02 -0500
commit582ce1f6e46989d278580d7f09a95f695164d876 (patch)
tree302e50949f676cb16eda96551fddb75e4b402200 /components/script/dom/bindings/codegen/parser/tests/test_namespace.py
parent2afaa4fcba7391eb0a9dbd6127cb8bac3af38ecb (diff)
downloadservo-582ce1f6e46989d278580d7f09a95f695164d876.tar.gz
servo-582ce1f6e46989d278580d7f09a95f695164d876.zip
Restyle hints for visited
Extend restyle hints to check additional cases for visited. If we are sensitive to visitedness and the visited state changed, we force a restyle here. Matching doesn't depend on the actual visited state at all, so we can't look at matching results to decide what to do for this case. This also updates the snapshot version of `match_non_ts_pseudo_class` to check the relevant link instead of the element state, just like we do when matching with regular Gecko elements. There's also a separate case of a visited-dependent selector when other state or attributes change. For this, we need to cover both types of matching we use when cascading values. If there is a relevant link, then we also matched in visited mode. Match again in this mode to ensure this also matches. Note that we never actually match directly against the element's true visited state at all, since that would expose us to timing attacks. The matching process only considers the relevant link state and visited handling mode when deciding if visited matches. MozReview-Commit-ID: CVGquetQ2VW
Diffstat (limited to 'components/script/dom/bindings/codegen/parser/tests/test_namespace.py')
0 files changed, 0 insertions, 0 deletions