Repository navigation
Add a test for hit testing to affect elements with 'opacity: 0' - #52375
Merged
Merged
Conversation
Psychpsyo
force-pushed
the
opacity-hit-testing
branch
from
May 6, 2025 23:40
4313fb0 to
a20a003
Compare
svgeesus
approved these changes
May 7, 2025
svgeesus
left a comment
Contributor
There was a problem hiding this comment.
LGTM
CSS Color 4 now updated, per WG resolution, to explicitly state that value of opacity does not affect hit testing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added this over in the Ladybird Browser, which did not handle this correctly: LadybirdBrowser/ladybird#4629
From what I can tell, this case is currently not covered.