Assigned
Status Update
No update yet.
Comments
ju...@google.com
I don't think this falls under pointer input so this is simply less tied to the area I've been focusing on. I think this should be considered open for anyone else to start working on. I think the two main areas of work for keyboard input are building out the equivalent of focusableInTouchMode and routing keyboard input events to the appropriate node/modifier.
Is this something that Semantics should handle? Seems that if it did, both keyboard events, auto fill, google assistant, could all use the same mechanism to send text data to the ui.
Is this something that Semantics should handle? Seems that if it did, both keyboard events, auto fill, google assistant, could all use the same mechanism to send text data to the ui.
Description
Version used: 1.5.0
Devices/Android versions reproduced on: All
I would like to raise a feature request to let the user define the maximum width each emoji should acquire when laid out inside the emoji-picker. At present it divides the available parent width by the span count to define its dimensions.
This leaves the user with only 2 options of
- either keeping the individual emoji size large
- or increase the span count (& thus making it look over-crowded from UX POV)
By providing an option to define a max emoji width we could use the additional space to define the padding between the icons, thus providing more control over how they are laid out in the picker view.
Possibly allowing to create a view like the one in attached screen shot.