Godot editor fields are less responsive : "Field Input" mode is too sticky

[Stealcase]

Godot version

Godot 4 Beta 3

System information

Windows 10

Issue description

2 Different issues with Tab Focus and field input mode.
Including both of in 1 issue because there seems to be some overlapping logic.

Scenario 1

Trying to navigate inspector properties with the Tab key, or quickly manipulate several fields.

Expected behaviour

When tabbing to an input field, I expect the input field to be focused and accept keyboard inputs. If I press tab again, I expect the next selectable input field to be focused and editable. This worked (mostly, with slight stickyness) in godot 3.5

Actual Behaviour

• Input fields sometimes become "Sticky", and don't allow continuous tabbing. When pressing the tab key, you are "soft selecting" the next property, while still stuck in "input mode" on the previous property. Tabbing/shift+Tabbing does NOT let you escape from this bug, only mouse clicking can help you.
• Only "Sticky" fields where the caret are visible are editable with the NumKeys. Other fields are "Focused", but cannot accept input until you press "spacebar" or "enter".

In-action in Godot 4 Beta 3

Spesific Example:

Freeze-frame of the "Stickyness". Pressing "Tab" while in this state will not let you exit.

Scenario 2

Trying to rename 1 or several files in the scene hierarchy.

Expected behaviour

1. Pressing tab while in the "Rename State" should switch focus to the next node below, and enter the Rename State. Pressing Shift + Tab should open the node above in Rename State.
2. Mouse clicking on Node Y while in Rename State on Node X should instantly exit Rename State on Node X, and select Node Y. This worked in Godot 3.5

Actual Behaviour

1. Pressing tab while in Rename State does nothing.
2. Clicking on another node while in rename state only exits the rename state: The original node retains focus.

Godot 4:

2 Clicks are required to select a new node.

Steps to reproduce

These are editor issues which can be reproduced in any node with input properties or scene hierarchies described above.

Minimal reproduction project

No response

[Riteo]

Does this behaviour happen in single window mode?

[Mickeon]

Yeah, this is kind of a regression of the way Popups are handled. They really do steal all inputs even if they do not make use of them. Very nice demonstration, it's difficult to put it to words, and it's really annoying. In Godot 4.0 you have to currently click twice to select another element. One time to have the Popup disappear, and another to reselect. This wasn't the case in 3.x, and really shouldn't be.

[Calinou]

Duplicate of #37723.