:in-range/:out-of-range should be a matter of using Style::PseudoClassChangeInvalidation instead of invalidateStyleForSubtree() where appropriate.
<rdar://problem/91718746>
Created attachment 459612 [details] Patch
Created attachment 459613 [details] Patch
Comment on attachment 459613 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=459613&action=review > LayoutTests/imported/w3c/web-platform-tests/css/selectors/invalidation/input-pseudo-classes-in-has-expected.txt:10 > +PASS :out-of-range invalidation There are cases this doesn't cover fwiw: - type attribute change - min/max attribute change Might be worth extending the test, and adding support if necessary
Created attachment 459637 [details] Patch
> There are cases this doesn't cover fwiw: > - type attribute change > - min/max attribute change > > Might be worth extending the test, and adding support if necessary Good future tasks.
Created attachment 459638 [details] Patch
Committed r294613 (250839@main): <https://commits.webkit.org/250839@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 459638 [details].