Split out of #174 so it stops living in a comment thread. Both points are from the submitter's colleague after testing (#174 comment), and both are the same underlying thing: contacts and calendar grew their menus at different times and it shows.
1. No hover menu button on the contacts list
Calendar page has the nav-more btn on hover. The contact page however does not have this nav-more btn on hover, but has a right-click menu.
The calendar exposes its per-item menu two ways — the dots button on hover, and right-click. Contacts only has right-click, which is undiscoverable and unavailable on touch. It should have the hover button too.
2. Import/export are global buttons and a per-book submenu
There are two main buttons for import/exporting contacts, while each address book has a submenu. Move those buttons to the address books submenu.
Two places to do the same thing, and the global pair doesn't say which book it acts on. The calendar settled this already: the iCAL import lives in the calendar's own dots menu and there is no global button, because that is where "which one?" is answered by where you clicked.
Why it's worth doing together
They're the same file and the same fix — make contacts follow the pattern the calendar already has, so there is one pattern in the app rather than two. Related: #216 asks for calendar export, which contacts already has; when that lands the two modules should agree on where import and export live.
Rebuilt from: session transcript.
Split out of #174 so it stops living in a comment thread. Both points are from the submitter's colleague after testing ([#174 comment](https://github.com/Coffey-Labs/ihasmail/issues/174#issuecomment-5507056538)), and both are the same underlying thing: contacts and calendar grew their menus at different times and it shows.
## 1. No hover menu button on the contacts list
> Calendar page has the nav-more btn on hover. The contact page however does not have this nav-more btn on hover, but has a right-click menu.
The calendar exposes its per-item menu two ways — the dots button on hover, and right-click. Contacts only has right-click, which is undiscoverable and unavailable on touch. It should have the hover button too.
## 2. Import/export are global buttons *and* a per-book submenu
> There are two main buttons for import/exporting contacts, while each address book has a submenu. Move those buttons to the address books submenu.
Two places to do the same thing, and the global pair doesn't say which book it acts on. The calendar settled this already: the iCAL import lives in the calendar's own dots menu and there is no global button, because that is where "which one?" is answered by where you clicked.
## Why it's worth doing together
They're the same file and the same fix — make contacts follow the pattern the calendar already has, so there is one pattern in the app rather than two. Related: #216 asks for calendar export, which contacts already has; when that lands the two modules should agree on where import and export live.
<sub>Rebuilt from: session transcript.</sub>
This repo is archived. You cannot comment on issues.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Split out of #174 so it stops living in a comment thread. Both points are from the submitter's colleague after testing (#174 comment), and both are the same underlying thing: contacts and calendar grew their menus at different times and it shows.
1. No hover menu button on the contacts list
The calendar exposes its per-item menu two ways — the dots button on hover, and right-click. Contacts only has right-click, which is undiscoverable and unavailable on touch. It should have the hover button too.
2. Import/export are global buttons and a per-book submenu
Two places to do the same thing, and the global pair doesn't say which book it acts on. The calendar settled this already: the iCAL import lives in the calendar's own dots menu and there is no global button, because that is where "which one?" is answered by where you clicked.
Why it's worth doing together
They're the same file and the same fix — make contacts follow the pattern the calendar already has, so there is one pattern in the app rather than two. Related: #216 asks for calendar export, which contacts already has; when that lands the two modules should agree on where import and export live.
Rebuilt from: session transcript.