Android Back key is incorrectly mapped to Delete

[victor_18993]

The Android Back key is currently mapped to

Code Select Expand

SIM_KEYCODE_DELETE in the SDL2 backend.
This normally goes unnoticed because both Escape and Delete close the top window when the event is not consumed first. However, a text input consumes Delete and removes the character under the cursor.
As a result, pressing Android Back while editing text deletes a character instead of following the existing Escape behaviour.
The attached patch maps

Code Select Expand

SDLK_AC_BACK to

Code Select Expand

SIM_KEYCODE_ESCAPE, while leaving the real Delete key unchanged.
The functional change is only:

Code Select Expand

- case SDLK_ESCAPE:     code = SIM_KEYCODE_ESCAPE;                break;
- case SDLK_AC_BACK:
+ case SDLK_AC_BACK:
+ case SDLK_ESCAPE:     code = SIM_KEYCODE_ESCAPE;                break;
  case SDLK_DELETE:     code = SIM_KEYCODE_DELETE;                break;

I checked the complete event path:

• Code Select Expand
  SDLK_AC_BACK is only mapped at this location.
• No Android-specific code intercepts it beforehand.
• Delete is consumed by text inputs and deletes a character.
• Escape leaves the text input without deleting text.
• When neither event is consumed, both already reach the existing top-window closing path.

Validation:

• Built successfully with the SDL2 backend on Windows 11 using MinGW-w64.
• Code Select Expand
  git diff --check is clean.
• Escape and the real Delete key remain unchanged.

I could not test the result on a physical Android device or a working emulator, so Android runtime testing remains pending.
Patch attached.

[prissi]

Delete closes all windows though. But maybe only closing the top window is even a better choice.