MCPE-31705Can't type in default input field until it's hovered over
The bug:
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.
To reproduce:
1. In creative mode, open your inventory
2. Begin typing letters – observe that nothing is happening
3. Hover over the "search" input box with your mouse, then hover off
4. Continue typing – observe that the field has started working
Affects:
- Creative menu
- Command blocks
- Anvils
- Writable books
Does not affect:
- Game chat
- Signs
More details:
After a field is selected, other fields can only be activated by clicking, not simply hovering. Essentially, the expected behavior is as follows:
- Default field immediately selected when GUI opened
- Select any field by clicking only, hovering alone should do nothing
- Clicking other buttons should deselect the selected field, with the exception of the creative menu, whose search bar should always be active if it's visible.
Linked Issues
- Unresolved
![[Mod] tryashtar](../../../data/avatars/users/41963.png)
[Mod] tryashtar- 15
- 3
- Confirmed
- 698006
- Windows
- accessibility ui
1.20.10.20 Preview - 1.21.51 Hotfix
1.20.10.20 Preview 1.19.80.21 Preview 1.13.0.1 Beta 1.18.10.26 Beta 1.17.40.23 Beta 1.17.40.21 Beta 1.17.20.22 Beta 1.17.10 1.17.20.20 Beta 1.17.0.50 Beta 1.16.210.53 Beta 1.16.0.51 Beta 1.14.1 Hotfix 1.14.0.2 Beta 1.13.0.9 Beta 1.12.0.11 Beta 1.12.0.2 Beta 1.11.0.10 Beta 1.9.0.0 Beta 1.2.13.11 1.2.14.3 1.2.13.54 1.4.3.0 1.5.0.10 1.6.0.1 1.4.2.0 1.6.0.5 1.5.0.14 1.7.1 1.7.0 1.9.0 1.10.0 1.13.0.4 Beta 1.14.0 1.16.0 1.17.2 Hotfix 1.17.30 1.17.32 1.18.2 Hotfix 1.19.70 1.19.83 Hotfix 1.21.21 Hotfix 1.21.51 Hotfix
Created Issue:
Can't type in default input field until it's hovered over
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.
To reproduce:
1. Open the creative menu
2. Begin typing letters except for T – observe that nothing is happening
3. Hover over the input box with your mouse
4. Continue typing – observe that the field has started workingThis affects the creative menu, command blocks, anvils, and writable books. It does not affect the game chat or signs.
In Java, all of these fields are editable as soon as they are made visible, excluding anvils (probably because it starts disabled until an item enters the interface).
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.
To reproduce:
1. Open the creative menu
2. Begin typing letters except for T – observe that nothing is happening
3. Hover over the input box with your mouse
4. Continue typing – observe that the field has started workingThis affects the creative menu, command blocks, anvils, and writable books. It does not affect the game chat or signs.
In Java, all of these fields are editable as soon as they are made visible, excluding anvils (probably because it starts disabled until an item enters the interface).
For interfaces with many input fields, it is expected that the first one be the default, and others can be switched to by clicking rather than hovering.
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.
To reproduce:
1. Openthe creative menu
2. Begin typing lettersexcept for T– observe that nothing is happening
3. Hover over the input box with your mouse
4. Continue typing – observe that the field has started workingThis affects the creative menu, command blocks, anvils, and writable books. It does not affect the game chat or signs.
In Java, all of these fields are editable as soon as they are made visible, excluding anvils (probably because it starts disabled until an item enters the interface).
For interfaces with many input fields, it is expected that the first one be the default, and others can be switched to by clicking rather than hovering.
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.
To reproduce:
1. Open a command block
2. Begin typing letters – observe that nothing is happening
3. Hover over the "command" input box with your mouse
4. Continue typing – observe that the field has started workingThis affects the creative menu, command blocks, anvils, and writable books. It does not affect the game chat or signs. The creative menu is special – you must begin typing while the mouse is currently hovered in order for the keys to start go through. All other fields can be hovered then exited before typing in order to enable them.
In Java, all of these fields are editable as soon as they are made visible, excluding anvils (probably because it starts disabled until an item enters the interface).
For interfaces with many input fields, it is expected that the first one be the default, and others can be switched to by clicking rather than hovering.
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.
To reproduce:
1. Open a command block
2. Begin typing letters – observe that nothing is happening
3. Hover over the "command" input box with your mouse
4. Continue typing – observe that the field has started workingThis affects the creative menu, command blocks, anvils, and writable books. It does not affect the game chat or signs. The creative menu is special – you must begin typing while the mouse is currently hovered in order
for the keys to start go through. All other fields can be hovered then exited before typing in order to enable them.In Java, all of these fields are editable as soon as they are made visible, excluding anvils (probably because it starts disabled until an item enters the interface).
For interfaces with many input fields, it is expected that the first one be the default, and others can be switched to by clicking rather than hovering.
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.
To reproduce:
1. Open a command block
2. Begin typing letters – observe that nothing is happening
3. Hover over the "command" input box with your mouse
4. Continue typing – observe that the field has started workingThis affects the creative menu, command blocks, anvils, and writable books. It does not affect the game chat or signs. The creative menu is special – you must begin typing while the mouse is currently hovered in order to enable it (after which you can continue typing regardless of the mouse's position). All other fields can be hovered then exited before typing in order to enable them.
In Java, all of these fields are editable as soon as they are made visible, excluding anvils (probably because it starts disabled until an item enters the interface).
For interfaces with many input fields, it is expected that the first one be the default, and others can be switched to by clicking rather than hovering.
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.
To reproduce:
1. Open a command block
2. Begin typing letters – observe that nothing is happening
3. Hover over the "command" input box with your mouse, then hover off
4. Continue typing – observe that the field has started workingThis affects the creative menu, command blocks, anvils, and writable books. It does not affect the game chat or signs. The creative menu is special – you must begin typing while the mouse is currently hovered in order to enable it (after which you can continue typing regardless of the mouse's position). All other fields can be hovered then exited before typing in order to enable them.
In Java, all of these fields are editable as soon as they are made visible, excluding anvils (probably because it starts disabled until an item enters the interface).
For interfaces with many input fields, it is expected that the first one be the default, and others can be switched to by clicking rather than hovering.
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.
To reproduce:
1. Open a command block
2. Begin typing letters – observe that nothing is happening
3. Hover over the "command" input box with your mouse, then hover off
4. Continue typing – observe that the field has started workingThis affects the creative menu, command blocks, anvils, and writable books. It does not affect the game chat or signs. The creative menu is special – you must begin typing
while the mouse is currently hoveredin order to enable it (after which you can continue typing regardless of the mouse's position). All other fields can be hovered then exited before typing in order to enable them.In Java, all of these fields are editable as soon as they are made visible, excluding anvils (probably because it starts disabled until an item enters the interface).
For interfaces with many input fields, it is expected that the first one be the default, and others can be switched to by clicking rather than hovering.
The bug:
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.To reproduce:
1. Open a command block
2. Begin typing letters – observe that nothing is happening
3. Hover over the "command" input box with your mouse, then hover off
4. Continue typing – observe that the field has started workingAffects:
- Creative menu
- Command blocks
- Anvils
- Writable books
- Creative menu (special case, you must begin typing while the mouse is hovered in order to enable it, hovering on then off will not activate it without typing in between)
Does not affect:
- Game chat
- Signs
More details:
After a field is selected, other fields can only be activated by clicking, not simply hovering. Essentially, the expected behavior is as follows:
- Default field immediately selected when GUI opened
- Select any field by clicking only, hovering alone should do nothing
- Clicking other buttons should deselect the selected field, with the exception of the creative menu, whose search bar should always be active if it's visible.
relates to
MCM-188
The bug:
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.To reproduce:
1. Open a command block
2. Begin typing letters – observe that nothing is happening
3. Hover over the "command" input box with your mouse, then hover off
4. Continue typing – observe that the field has started workingAffects:
- Creative menu
- Command blocks
- Anvils
- Writable books
- Creative menu (special case, you must begin typing while the mouse is hovered in order to enable it, hovering on then off will not activate it without typing in between)
Does not affect:
- Game chat
- Signs
More details:
After a field is selected, other fields can only be activated by clicking, not simply hovering. Essentially, the expected behavior is as follows:
- Default field immediately selected when GUI opened
- Select any field by clicking only, hovering alone should do nothing
- Clicking other buttons should deselect the selected field, with the exception of the creative menu, whose search bar should always be active if it's visible.
relates to
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
The bug:
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.To reproduce:
1.Open a command block
2. Begin typing letters – observe that nothing is happening
3. Hover over the "command" input box with your mouse, then hover off
4. Continue typing – observe that the field has started workingAffects:
- Creative menu
- Command blocks
- Anvils
- Writable books
Does not affect:
- Game chat
- Signs
More details:
After a field is selected, other fields can only be activated by clicking, not simply hovering. Essentially, the expected behavior is as follows:
- Default field immediately selected when GUI opened
- Select any field by clicking only, hovering alone should do nothing
- Clicking other buttons should deselect the selected field, with the exception of the creative menu, whose search bar should always be active if it's visible.
The bug:
Most text input fields are un-editable until the cursor hovers over it. This makes it disruptive to, say, open a command block and immediately begin typing.To reproduce:
1. In creative mode, open your inventory
2. Begin typing letters – observe that nothing is happening
3. Hover over the "search" input box with your mouse, then hover off
4. Continue typing – observe that the field has started workingAffects:
- Creative menu
- Command blocks
- Anvils
- Writable books
Does not affect:
- Game chat
- Signs
More details:
After a field is selected, other fields can only be activated by clicking, not simply hovering. Essentially, the expected behavior is as follows:
- Default field immediately selected when GUI opened
- Select any field by clicking only, hovering alone should do nothing
- Clicking other buttons should deselect the selected field, with the exception of the creative menu, whose search bar should always be active if it's visible.
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
![[MCQA] v-weszaj](../../../data/avatars/users/18941.svg){kind=small}
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
I could only reproduce this with anvils, books and quills, and the Creative menu.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version?
If it is, please be sure to include steps to reproduce the problem:
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Still an issue in 1.16.210.53 Beta.