nextcloud / nextcloud/mail

No activity indication is given when fetching from mail server

Open
#3,286 8 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug enterprise papercut
Dominant language
JavaScript
Stars
1k
Forks
348
Avg merge
12h 28m
Merged PRs (30d)
91

Description

Expected behavior

After logging in to Next Cloud and opening Mail, some indication that it is still loading new messages from the server should be given, so that it is possible to tell the different between "no new mail" and "still loading new mail".

Actual behavior

On opening mail, there is no indication it is doing anything. Maybe you have new mail, maybe you don't. Who knows?

This is aggravated somewhat by it seeming to take a long time to check for new mail in the first place, but that's probably a separate bug.

Mail app

Mail app version: 1.4.0

Mailserver or service: Dovecot

Server configuration

Operating system: Debian 10

Web server: Apache

Database: MariaDB

PHP version: Whatever comes with Debian 10

Nextcloud Version: 19.0.0

Client configuration

Browser: GNOME Web 3.36.2

Operating system: Ubuntu 20.04

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the Mail app: open Mail and observe the fetch for new messages. Trace the existing loading behavior in the frontend; done means a visible indication distinguishes an in-progress fetch from having no new mail.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.