mail
mail copied to clipboard
Dogfooding issues, from design glitches to missing functionality
Have been using the Mail app exclusively for the past few weeks, here are some findings.
@ChristophWurst @GretaD @karlitschek it is roughly sorted/prioritized as the top group is regressions and things related to the new design, while the bottom group is more missing features.
Since the update to latest on tech-preview
- [x] ~~Long mails do not scroll anymore~~
@nextcloud/vue@6doesn't work with Nextcloud 25. v2 will come with @7 and scroll again - [x] https://github.com/nextcloud/mail/issues/7098
- [ ] "more actions" button in message list does not have clear border on focus
- [x] Unread indicator in left navigation
- [x] https://github.com/nextcloud/mail/issues/7769
- [x] https://github.com/nextcloud/mail/issues/7182
General
- [x] ~~Whitespace in the nav on top towards the header, and on the right between scrollbar and message list, and in settings scroll area to the right and bottom. Padding needs to be used instead of margin~~ issue of nc/vue@6, fixed with 7
- [x] ~~Settings button in bottom left does not use border-radius-pill~~ issue of nc/vue@6, fixed with 7
- [x] https://github.com/nextcloud/mail/issues/7153
Writing
- [x] https://github.com/nextcloud/mail/issues/5060
- [x] https://github.com/nextcloud/mail/issues/7125
- [x] https://github.com/nextcloud/mail/issues/9452
- [x] Drafts remain when message is sent https://github.com/nextcloud/mail/issues/4768
Priority inbox
- [ ] The entry is called "Priority inbox" but the action and heading is called "Important". We should standardize this. Which one do you prefer?
- [ ] We could keep "Priority inbox", then use "Priority" as heading, and "Priority"/"Not priority"
- [ ] Or we go with "Important inbox", "Important" as heading, and keep "Important"/"Unimportant" for the actions.
- [x] Mails shown in "Priority" repeat in the "Other" section below, but should not be duplicated. https://github.com/nextcloud/mail/pull/7187
Message handling
- [x] Archiving messages is manual https://github.com/nextcloud/mail/issues/22
- [x] When marking message as spam, it is not directly deleted / moved to spam https://github.com/nextcloud/mail/issues/4101
- [x] Multiselect menu missing "Mark as spam" and "Tags" https://github.com/nextcloud/mail/issues/7006
- [x] Ability to empty spam/junk all at once https://github.com/nextcloud/mail/issues/6060
~~What version did you test with?~~
v1.14.0 beta 2
Does not line up with 3-dot-menu
https://github.com/nextcloud/nextcloud-vue/pull/3178 or is this about some other alignment?
Does not line up with 3-dot-menu
nextcloud/nextcloud-vue#3178 or is this about some other alignment?
Yes, it is actually that one, but see my comment: https://github.com/nextcloud/nextcloud-vue/pull/3178#issuecomment-1238179570
It's really nice to see someone on the inside using mail as their daily driver. As a regular user myself, I can confirm that I regularly notice most of the same issues/annoyances (I'm on 1.14.0-beta1).
A few issues that I'm surprised weren't listed are: #7036 and "Selecting message opens new browser tab" (perhaps this is fixed in the latest beta that is not available via the store yet).
It's really nice to see someone on the inside using mail as their daily driver. As a regular user myself, I can confirm that I regularly notice most of the same issues/annoyances (I'm on 1.14.0-beta1).
A few issues that I'm surprised weren't listed are: #7036 and "Selecting message opens new browser tab" (perhaps this is fixed in the latest beta that is not available via the store yet).
we have done couple of other pre-releases: https://github.com/nextcloud-releases/mail/releases
Thanks @GretaD . I just udpated to the latest beta (https://github.com/nextcloud-releases/mail/tree/v1.14.0-beta3) and still seem the same issues i mentioned above. I don't currently see a way to upgrade to the v2.0 line of releases in Nextcloud 24. Is this possible without having to git clone the repo?
Hello @meichthys, so sorry i missed your message. Are you still having this issue?
Hi @GretaD, #7036 is still an issue for me, but the new-tab issue is fixed in 2.0.0-beta.6 👍