Ability to add the exact time to message overview
Checklist
- [X] I have used the search function to see if someone else has already submitted the same feature request.
- [X] I will describe the problem with as much detail as possible.
- [X] This issue only contains a request for one single feature, not multiple (related) features.
App version
6.801
Problem you are trying to solve
On some occasions, you will be getting several messages in a day which have the exact same topic title. With only the date as a distinguisher, it is sometimes very hard to identify the mail you're looking for.
Suggested solution
It would be great if the overview could always show the time the mail was received, regardless of the date. Similarly, I'd prefer K-9 to consistently show the date instead of displaying "Mo" for a mail that was received six days ago (I'm sure this was done with the best of intentions, but it really makes things more complicated).
Of course, displaying this information could be optional.
Screenshots / Drawings / Technical details
No response
Should be the default. But at least having an option to show time would be good too.
I agree, the format of time and date in the overview should be a user option.
This might be a major UI change or maybe simpler to implement than I think. Adding a sticky bar at the top(of email list) for showing full date, and day. With the right most place on email cards reserved for time.
This way as the user scrolls, the top sticky bar would update only if the user scrolls through to a different day.
At any point while on email list screen, full date and time for each email are always in view.
Ref : similar to how position: sticky works
I think this is interesting to explore, the sticky headers idea sounds like good idea. I'm confirming this, but can't promise any immediate action. For someone wanting to pick this up let's have a chat via Matrix or on this issue, maybe with the design folks included, to see what is the best option.
Does this need a separate issue or is this covered by #3987?
@cketti I think this issue(my recommended implementation with sticky elements) is dependent on #3987
Maybe it can be paused in favor of this.