Composer issues

Yes, I have also found this, I just tried typing a very long reply. When I tried to replicate the issue, I was only making a short reply so it does not expand the text window. I guess it is back to creating replies off line, pending a resolution. I have since deleted my earlier reply to renchap.

When it comes to previewing, a message, wouldn’t it be better to simply add a “preview” button somewhere, rather than compromising the usability of, a solution that is well-thought-out and valued by users?

And yes maybe it will force to have different solutions for desktop and mobile but IMO it is perfectly fine. Better than limiting the capabilities of the desktop client just because mobile phones happen to be poor tools for web-based applications.

2 Likes

The position of the new box is not ergonomic. I shouldn’t have to look down at the thing I’m focusing on. At the very least I need to be able to move the compose box into the center area of the screen.

I get the point that there’s a lot of button in the compose box, but the new box shows FEWER of them, hiding things like visibility and content warnings behind the dots menu.

3 Likes

If the team wishes to maintain the current composer box design, I see a possible solution to consider. Keep the composer box at its current size, and rather than expanding as further text is added, enable the user to scroll up and down the text they are typing, and at the same time scroll up and down the post behind that they are replying to, so it can be easily read whilst replying.
The composer box could also made as a floating composer box so the user can move it around the screen, this may aid composing messages/replies.
I am not sure how any of this would work on mobile phones.
Maybe it is just better to return the composer to the previous version.

2 Likes

Thanks for the feedback, everyone. Two things that should help here, that are planned, but that we simply couldn’t achieve in the timeline required for the 5.0 release:

  • Inline replies. From a post’s page, reply inline and scroll wherever without losing context. Expand to the full composer if desired.
  • Docking options and preferences. Select from full-screen, bottom right, or top right… and your composer essentially stays where you most prefer it.

For 5.0, we’ve made the change to a center modal composer. This is based on feedback about composer positioning on larger screens and the advanced UI that won’t be resolved by simply trying another position. I realize this may be frustrating, but there’s no good way to prevent blocking the content without creating a subpar experience for other cases – until we’re able to implement the two bullet points mentioned above.

There are several valid points made in this thread. But a post with several requests can’t be organized or voted on effectively, which makes it less likely that your feedback will be resolved. I’ve closed this topic so anyone can post specific feedback (e.g. “I can’t see the context of what I’m replying to”). If you choose to do that, please search first, since some topics may already exist (you can simply upvote them in that case). More on this in our App Feedback Guidelines.

1 Like