Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No back navigation when reading email #7

Open
bunyevacz opened this issue Jun 7, 2018 · 3 comments
Open

No back navigation when reading email #7

bunyevacz opened this issue Jun 7, 2018 · 3 comments

Comments

@bunyevacz
Copy link

bunyevacz commented Jun 7, 2018

Let's say we are on the 5. page of inbox, and reading an email.
Now there is no way to navigate back to the 5. page of the inbox, after I finished reading the current email.
(it always navigate back to the first page of inbox)

The browser's back button is not a solution, because if I replied or forwarded an email, it will not navigate back to the inbox. Also the browser's back button does not mark 'read' the last readed email.
(users assumed that this feature (removing bold of a readed email) is not working)

I think it is rather a minor feature to implement, because we can maybe determine the url where we are coming from.

I have not looked around deeply in the source code. But maybe easier then attachment forwarding.

This is a major complain from the users.

@andris9
Copy link
Member

andris9 commented Jun 7, 2018

I guess it would be doable. It would require to drag along the listing information, probably in a hidden field, so it would not get lost on forwarding or such.

@bunyevacz
Copy link
Author

@andris9 :

It may be a little too early, but I'm playing with the idea, to have a rich email client,
just like gmail. I would implement it with react.

It would feature auto draft save (just like gmail),
multiple file attachment (with progressbar when attaching), deleting all emails in trash (800+ emails, one-by-one so the server only gets one delete at a time, or in chunks (10 at a time)).

Still a server side rendering (like now) is useful. Gmail calls it Load basic HTML.

So my question is:

  1. do you like the idea?
  2. should I implement it inside wildduck-webmail or in a separate repo ? (I would like to implement it here, to get your advises and expertises).

I dont want to look too overproud of myself, but I may be able to pull it off (of course with a pair of your expert eyes, to not do anything too stupid).

@andris9
Copy link
Member

andris9 commented Sep 11, 2018

One of the reasons for the API based access to the email backend was to enable custom UIs. The existing webmail is more like a demo, I'd rather keep it as simple as possible, so I'd suggest you to fork the current webmail and build on top of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants