patch 9.1.1826: Patch v9.1.1230 causes confusion about Ctrl-C behaviour

Problem:  Patch v9.1.1230 causes confusion about Ctrl-C behaviour
          (kuuote, after v9.1.1230)
Solution: Revert the behaviour, keep the old behaviour

fixes: #17266

Signed-off-by: Christian Brabandt <cb@256bit.org>

src/popupwin.c

@@ -3622,20 +3622,6 @@ popup_do_filter(int c)
 		&& (wp->w_filter_mode & state) != 0)
 	    res = invoke_popup_filter(wp, c);
 
-    // when Ctrl-C and no popup has been processed (res is still FALSE)
-    // Try to find and close a popup that has no filter callback
-    if (c == Ctrl_C && res == FALSE)
-    {
-	popup_reset_handled(POPUP_HANDLED_2);
-	wp = find_next_popup(FALSE, POPUP_HANDLED_2);
-	if (wp != NULL)
-	{
-	    popup_close_with_retval(wp, -1);
-	    res = TRUE;
-	}
-    }
-
-
     if (must_redraw > was_must_redraw)
     {
 	int save_got_int = got_int;

src/testdir/test_popupwin.vim

@@ -3931,7 +3931,7 @@ func Test_popupwin_cancel_with_without_filter()
 
   call feedkeys("\<C-C>", 'xt')
   call assert_equal({}, popup_getpos(win1))
-  call assert_equal({}, popup_getpos(win2))
+  call assert_equal(10, popup_getpos(win2).line)
 
   call popup_clear()
 endfunc

src/version.c

@@ -729,6 +729,8 @@ static char *(features[]) =
 
 static int included_patches[] =
 {   /* Add new patch number below this line */
+/**/
+    1826,
 /**/
     1825,
 /**/