Please relocate the "saving/saved" bar at the upper right corner of the Task Description
planned
Erik Phillips
The "saving/saved" bar at the top right corner of the Task Description covers a few words of the first line in the Task Description (see screenshot). I appreciate its inclusion and its utility; its placement is just a little inconvenient.
Log In
b
benjaminclark
Yeah, that overlap can be a bit distracting, especially when you’re trying to quickly scan the first line, hopefully something like LemLedger https://lemledger.com/ considers small UI tweaks like repositioning for better readability.
Raina Ahuja
Merged in a post:
Hide Toast/Snackbar of the Task Description for autosaving status
A
Antonio Villa
Hide the toast o snack that gets displayed on the top right of the text area where we enter the description of the task that displays that the content has been saved, it blocks the portion of the text and it makes it hard to read the content of the description. See screenshot below. You can display this information outside the text area so that it does not block the content of the description.
Raina Ahuja
Merged in a post:
Fix the “Saved” tooltip that hides the body of text on the Task view
Q
Quentin Villeroge
In the body of a task, the tooltip is displayed above the text when writing. It's annoying.
Brendan W
Merged in a post:
Save status : Overlapping text in task description
T
Tymothée Martin
When you change a task description, the save status appears over the text, which is really annoying.
Raina Ahuja
Merged in a post:
Remove the TERRIBLE UI on the Task Description
D
Dan Jacquemin
1) Not every dang bit of text on your site needs a hidden menu. Enough already.
2) The Task Description has a terrible little menu that shows up in the upper right, OVERLAYING ACTUAL CONTENT. The overlay only exists to expand the description... and that is only needed because your terrible UI covers user content. Enough is enough already.
Raina Ahuja
marked this post as
planned
Raina Ahuja
Erik Phillips Thank you for the feedback! We're iterating on a fix for this now, stay tuned.