Page MenuHomekolab.org

No undo button after deleting Calender
Open, NormalPublic

Description

After deleting an event it there appears an undo button for 10 seconds. There should be the same possibility to undo a deleted calender.

Steps to reproduce:

  1. click on calender
  2. delete calender
  3. click ob delete in dialogue window

Actual result:
there appears a pop-up that the calender was deleted

Expected result:
The pop-up has a button to undo the delete (for 10sec).

Details

Ticket Type
Task

Event Timeline

isabel.pacheco moved this task from Backlog to 1 on the UX Seminar WS17 board.Dec 14 2018, 2:02 PM
isabel.pacheco triaged this task as Normal priority.
bohlender added a subscriber: bohlender.

Sounds like a good idea to me.

Undeleting a folder requires administrator rights in IMAP. So, such a feature would have security implications and needs more considerations.

Couldn`t we just delay the deletion for 10 sec?

Well, we could. We'd need to store the deletion request for later in some persistent storage and take it from there after timeout. What about a case when a user deletes the calendar and immediately leaves webmail session? Should he then expect the calendar to be deleted on his iPhone? In other words, we could do this on client side only, no IMAP technology (I know of) to do this server-side.

Maybe @vanmeeuwen would have some ideas.

What about a case when a user deletes the calendar and immediately leaves webmail session?

In that case the user would expect the deletion to still go through.

Could we start with two "random" autocomplete suggestions - one beeing a name, the other an email address?

You mean display autocompletion list when you focus the input without entering anything (yet)? Sounds strange. Also, note that autocompletion does not display names and email separately (until, of course there a person without a name specified).

You mean display autocompletion list when you focus the input without entering anything (yet)?

Or when you type the first letter. Its probably a bad idea.

We could just have an "alice@example.com" placeholder text.
The user will eventually get an autocomplete suggestion for a contact anyway.
So after some time the user will realize that he can also type names.

I think this is non-issue. You don't consider "alice@example.com" also confusing?

The issue is that test subjects were confused on what to to type in this field.
So we need some way to show them what kind of data belongs in that field.
A (greyed out) placeholder text is on UI pattern that solves this quite well.