New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change unclear Color::isValid() to explicit isCurrentColor(). #4528
Change unclear Color::isValid() to explicit isCurrentColor(). #4528
Conversation
EWS run on previous version of this PR (hash 12c3b9d) |
12c3b9d
to
20fd0a0
Compare
Please describe why this change is valid, so it's clear to other people reading the patch. Also, |
20fd0a0
to
87eef41
Compare
EWS run on current version of this PR (hash 87eef41)
|
https://bugs.webkit.org/show_bug.cgi?id=245424 Reviewed by Antoine Quint. Due to the representation of "current color" as "invalid color" in WebCore, they are two functionally equivalent functions in the codebase: - Color::isValid() - RenderStyle::isCurrentColor(Color) which is implemented as "return !color.isValid()". The second one makes the intention of the check clearer and should be preferred. * Source/WebCore/animation/CSSPropertyAnimation.cpp: * Source/WebCore/svg/properties/SVGAnimationAdditiveValueFunctionImpl.cpp: (WebCore::SVGAnimationColorFunction::calculateDistance const): Canonical link: https://commits.webkit.org/254683@main
87eef41
to
0b28244
Compare
Committed 254683@main (0b28244): https://commits.webkit.org/254683@main Reviewed commits have been landed. Closing PR #4528 and removing active labels. |
0b28244
87eef41
π macπ§ͺ api-iosπ§ͺ api-macπ§ͺ api-gtkπ§ͺ mac-wk1π§ͺ mac-wk2π§ͺ mac-AS-debug-wk2π§ͺ mac-wk2-stress