Steps to reproduce
Open the creative inventory (press "e").
Hover over an item in the creative inventory with the mouse pointer.
Press "q".
Expected result
You drop the item that you are hovering over.
Observed result
You type "q" in the search bar.
cant press q on keyboard when in creative inventory
Attachments
Comments 3
I cant press the q key on my keyboard when im the creative inventory but when i go to my other inventory it lets me drop all the items
This is a result of a change stated in the 1.19.80.21 changelog:
Search bar in Creative inventory screen is now automatically selected while using a keyboard
Although listed under "Vanilla Parity", this change is not parity, but in facts breaks parity. In Java Edition 1.19.4 the creative menu behaves just as the "Expected Results" state.
Even if Java is changed to highlight the search bar by default, I would not consider it parity to make Bedrock do the same because the entire creative inventory is fundamentally different between editions. The Bedrock creative inventory is much more oriented toward visual and mouse/touch/controller-based navigation: its broad view shows more than twice as many items as Java's small window; it is divided into a smaller set of tabs, and it uses nested groupings for many item types. Forcing the focus to the search bar just makes the inventory more difficult to use.
I actually use the hover + q or hover + ctrl + q feature a lot in creative to give items to mobs or drop them in hoppers, or even to give them to myself when my hotbar is full. I never use the search bar, nor do my kids. It's actually uncomfortable to have to think about about the spelling of an item when you are looking for it; it forces you to shift attention to a different part of your brain.
There are q's shown in the screenshot. Please provide more details. The following format is requested:
(add screenshots or video to help explain the issue)
This report has been temporarily closed as Awaiting Response. It will automatically reopen when you add information. Please follow the format shown and include all sections (steps, observed, expected). Reports that do not contain all of the requested information and complete steps to reproduce the issue may be closed as Incomplete. For more information please read the Bug Tracker Guidelines.
You may find this Report Creation Form helpful for any future reports you create.