In a UX-focused discussion titled ‘Composer button bar suggestions,’ Don proposes CSS-based UI improvements to fix mobile editor usability issues, particularly where native context menus and selections obscure the button bar. His solution moves the button bar to the bottom on mobile and repositions popup menus to avoid overlap. Screenshots and a video demonstrate the changes, which users like hoangphuctran93 and nathank praise for significantly improving mobile experience. jidanni suggests testing on devices with minimal input space. However, Jagster reports conflicts with the AI helper, which Don later addresses by repositioning the AI icon to the top-right with fixed positioning and disabling animations Don. While this works on iPhone, Jagster notes the settings cog opens oddly within the bar, and the AI icon disappears unless the bar is hidden. Don clarifies his AI fix is additive, not a replacement, and admits combining both modifications may not work due to layout conflicts Don. Heliosurge requests fixes for Android keyboard overlap, which Don suggests might require padding or a separate UX thread. Heliosurge also adds CSS to fix character count overlap. Later, Heliosurge notes the button bar no longer scrolls to reveal hidden items. Meanwhile, sam reminds users of the new proofreading shortcut via the cog, which Jagster finds helpful but still misses other AI features. The thread reflects ongoing community collaboration to refine mobile composer UX, with some solutions working partially or requiring further iteration.
This is a common issue on our forum. The native mobile context menu and selection is make complicate to use the editor button bar. So I made some hacky changes (need more work) but I think this is good, for an idea…
I show an example.
Sounds wonderful. Please also test on devices where you only have three lines in the input window. Not about 12 as in your first screenshot. Such a tiny window to edit here on a cell phone
Was wondering if you might have a solution for mobile Android Keyboard.
On Google Pixel 8 and possibly other android phones. When using the code editor in Customization > Theme & Customization > Theme component, the keyboard covers the area being inputted if there is a lot of code and bottom areas. This also happens in the code editor for the new Form-templates.
If I am understanding this can likely be fixed by adding padding to the bottom? So keyboard is only covering empty area?
I’ve placed the AI to top right. I think it won’t interfere anything and the expanded options is full width top. I disabled the animations to prevent flashing while selecting. Not too tested code but something… I think it should work iPhone too but I didn’t test it so please test before go live. The composer is always in full height.
@Heliosurge, I am not sure about this but if it’s a common issue or core issue than I think it worth to open a new Contribute > UX topic with some screenshots / video…
Yeah, it seems not work with reverse column or other ordering. So I think if it isn’t work with this then we can’t do too much to combine these two modification.
I’ll looking for a new workaround to makes it work and redesign things a little bit…
Bummer. Because for me, as a layman, that sounds like change of Discourse how to show AI helper broke several things in Apple-devices, because your solution worked earlier