From 5d08806adf128809857bb1ed57bfe49e7148fd1c Mon Sep 17 00:00:00 2001 From: Jonas Kvinge Date: Mon, 11 Oct 2021 21:05:28 +0200 Subject: android: Fix typo in source code comment Change-Id: Ieeab35d51588cf247c3d9626d0291e2983720873 Reviewed-by: Kai Koehne --- src/plugins/platforms/android/qandroidinputcontext.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/plugins') diff --git a/src/plugins/platforms/android/qandroidinputcontext.cpp b/src/plugins/platforms/android/qandroidinputcontext.cpp index aac0ba2c89..417f3469a8 100644 --- a/src/plugins/platforms/android/qandroidinputcontext.cpp +++ b/src/plugins/platforms/android/qandroidinputcontext.cpp @@ -1029,7 +1029,7 @@ jboolean QAndroidInputContext::deleteSurroundingText(jint leftLength, jint right absolutely not what Android's native EditText does. It deletes leftLength characters before min(selection start, composing region start) and rightLength characters after max(selection end, composing region end). There are no known keyboards that depend on this behavior, but - it is better to be consistent with EditText behavior, because there definetly should be no + it is better to be consistent with EditText behavior, because there definitely should be no keyboards that depend on documented behavior. */ const int leftEnd = -- cgit v1.2.3