Alphabet List Always Treated as Top Layer

[HDFLucky]

Describe the bug

When a custom widget with right side controls is visible, those controls cannot be accessed because the alphabet list is treated as top layer (i.e., Alphabet "jumps" up instead of activating the widget control). This is true even if Alphabet is hidden.

Steps to reproduce

1. Add a custom widget with right-side controls (e.g., Flipboard, the Google search widget in Pix Material You Light/Dark, or most music players).
2. Attempt access to those control(s) (e.g., the up/down story select icons in Flipboard or the Lens icon in Pix Material You search).
3. The alphabet list jumps up instead of the widget control being acted upon. This is true even if the Alphabet is hidden (it momentarily becomes visible when you touch the right side of the widget).

Does the issue also occur with other 3rd-party launchers?

Not applicable

Other 3rd-party launcher(s) tested

No response

Device name

Motorola Razr+

Android version

Android 13

Screenshots / Screen recordings

No response

[HDFLucky]

I saw the response to issue #1714, which was to state this is expected behavior and done intentionally "because you don't want the widget to always take precedence over the alphabet." Please reconsider and look into this again, since in most cases, it will never interfere. Further, the suggestion, "we recommend to not activate full screen mode if it has buttons at the edges" actually makes the problem worse (see screenshots, below).
Full-screen:

Normal:

The alphabet is a full 1.5 inches below the widget controls. Granted, my alphabet list does not contain the letters B, I, J, Q, but even if it did, it would still be a full inch below the Poweramp widget controls. As you can see, following the advice to not use full-screen makes the widget totally unusable. There is no possibility of the full-screen widget interfering with alphabet access. Even the most basic and free launcher can reserve screen areas (e.g., "system tray"). With the number of people complaining of this issue (ticket #s 1525, 1714, 1760, 2127, 2377, 2390, 2436.... these are just the one I know of), a solution or user-configurable option is needed.