Odd. What theme are you using?
“Meta Branded” - I had to look that up in preferences, as I don’t think I have ever changed it.
Okay yeah, so it’s just an issue with that theme that is using a different fontset that doesn’t map great. Doesn’t happen with themes that use the default fonts (like foundation or Horizon).
Ok, thanks for the clarification.
User feedback then composer is in “Standard Markdown Editor” the reply button is way to the right (desktop, default and default dark themes). Yes muscle memory but users are users
I like the redesign overall but one issue that I have found is that, because I am An Old™, in the desktop breakpoint my normal behavior is to craft my response and then press tab and enter to submit the post. This worked accurately in the old version but this experience has the Markdown editor button as the element that takes focus if you tab out of the div that behaves as a textarea.
This has effectively broken keyboard navigation because I either need to press tab five times or use the mouse. Can this behavior be updated so that the Reply button takes focus on tab out of the compose textarea? I would argue that a large majority of users simply want to post their reply rather than use any of the formatting options on a regular basis.
Hey @BeefofAges
I see where you’re coming from, unfortunately changing the tab order to skip this element isn’t really a great experience for the visually impaired users.
However, good news, because we have a built-in shortcut to post a topic: cmd/ctrl + enter should do the trick, no matter where you are focussed.
Appreciate the clarification, and I agree that a11y and WCAG issues take precedence.
This old dog will need to learn new (muscle memory) tricks. ![]()
We tested it on our community which is mostly mobile-based. We’re excited for the focus the mobile UX will be getting, but a few users have reported issues with the missing toolbar.
It sounds similar to what @ars18 mentioned. I couldn’t replicate it myself, but here’s a screenshot of a user’s composer. It seems that his toolbar never animated in (just a guess?). On my device, after a short delay, the toolbar animates in with a slide up.
Ru-roh, not good. Can you get me some more specifics on device, OS, browser, and browser version?
Oh I ran into this before and forgot about it — if you disable the toolbar before the redesign is enabled, the toggle no longer exists and you can’t toggle it back on.
This will ignore the state when the redesign is enabled
You can also fix this manually by clearing discourse_toolbar-enabled from your browser’s localStorage (though this can be a little tricky to find on mobile)
As i started a topic on the Arduino forum with this exact question and was referred here, i found the mention of this. I understand it is probably better for most, but not for me. I’m working on a laptop and somehow the buttons seem to slide of my screen down the bottom where i need to scroll and look for them when creating larger posts that require me to look things up in the thread, whereas they were always accessible directly when they were at the top.
Could be just that my scrolling is the issue
But this is what happens to me. Maybe it could be made user configurable ?
I think so, that’s not at all the normal design ![]()
Can you try in safe mode to see if it does the same?
That is the normal design on the Arduino forum i think.
In safe mode the composer option appear at the top again (i think), It took a bit of effort to log in, i probably have 2 accounts now, ah well.
I think it’s a combination of zoom and scroll that causes them to slide off the moment that i scroll up through the thread and they don’t re-appear until i scroll all the way down again.
It happens many times i refer to a bit of code in a previous post and sometimes these threads can be lengthy and i have to scroll through and back down and then back up. If it is possible to have the options at the top, that would be better for me.
The zooming in is of course a response to the layout being optimized for portrait rather than landscape. I guess one could call it a workaround to optimize the screen space.
Oh I meant: the scrolling away of the buttons is not the normal design.
I think it’s a combination of zoom and scroll that causes them to slide off the moment that i scroll up through the thread and they don’t re-appear until i scroll all the way down again.
Are you saying it only happens when you are zoomed in on the page?
Are you saying it only happens when you are zoomed in on the page?
Ah yes, but i am always zoomed in as a result of the portrait optimized layout.
Regardless the composer options used to be at the top, and the issue didn’t exist practically.




