-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[WPE] Click count leaking through successive layout test within the same WPEView #47417
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
base: main
Are you sure you want to change the base?
Conversation
…ame WPEView https://bugs.webkit.org/show_bug.cgi?id=295252 Reviewed by NOBODY (OOPS!). Add a new function to reset click count tracking between tests, avoiding accidental double and triple clicks. Found this issue while rebaselining the fast/html/details-* tests after 296203@main. Some rebaselines were flaky as the tests were affected by this when running together. * LayoutTests/platform/glib/fast/html/details-*-expected.txt: Rebaselined. * LayoutTests/platform/gtk/fast/html/details-*-expected.txt: Rebaselined. * LayoutTests/platform/wpe/fast/html/details-*-expected.txt: Rebaselined. * Source/WebKit/WPEPlatform/wpe/WPEView.cpp: (wpe_view_clear_press_count): Added. * Source/WebKit/WPEPlatform/wpe/WPEView.h: * Tools/WebKitTestRunner/wpe/TestControllerWPE.cpp: (WTR::TestController::platformConfigureViewForTest): Reset click count between tests.
EWS run on current version of this PR (hash 17c9db0) |
* wpe_view_clear_press_count | ||
* @view: a #WPEView | ||
* | ||
* Clear any button press being tracket. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo: tracket.
@@ -138,6 +138,7 @@ WPE_API guint wpe_view_compute_press_count (WPEView | |||
gdouble y, | |||
guint button, | |||
guint32 time); | |||
WPE_API void wpe_view_clear_press_count (WPEView *view); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems counter-intuitive that an external entity has to tell the view that it has to clear something, because of a navigation/load action. I guess there is never a situation where we want to preserve that press count between such events, no?
17c9db0
17c9db0