We still might need to use the "switch" instead of a standard checkbox on desktop. It's e.g. when you have a selectable list like the folders list, where you would use checkboxes for multi-selection and switches for subscription change. Also, I think these days users are used to know switches as everybody saw them on their mobile. Though, I don't have a strong opinion about that. Maybe we should indeed not use them on desktop.

I agree. Right-click functionality is provided by an external plugin. I created a ticket there https://github.com/johndoh/roundcube-contextmenu/issues/103. We'd need also such functionality for Kolab plugins that add Settings sections i.e. kolab_activesync and kolab_delegation.

The old-old skin displayed these messages on top-center. Then we created a new skin that displays them in right-bottom. I think back then the reason was to not overlap buttons with them. We had not much complaints about that since. On the other hand there were complaints about these notifications being distracting. So, I'm looking for a compromise here. If we put them in right-bottom, but make them more distinct, it could maybe work, if we do not touch the (quite often) "loading" message (so this one is not so much distinct).

Maybe changing the background color to be dark would fix that. E.g. https://github.com/roundcube/elastic/issues/38#issuecomment-329355387

I think so. We considered this issue in the past and I think we cannot do more until Firefox fixes it.

This is Firefox-specific and cannot be changed. https://github.com/roundcube/roundcubemail/issues/5125

I guess on iOS the field have to be defined as <input type="email"> to get "@" in default keyboard. However, you can configure Roundcube to allow usernames that aren't email addresses, so it's not as simple as switching type=text to type=email.

Technicly we could do the same we do with special mail folders yes, but...

1. Kolab allows subfolders and we often have "Contacts > Personal Contacts" folders too. Translating also this one would be problematic, as well as translating only it's parent.
2. Roundcube/Kolab allows global (ldap) addressbook, it's name is also not localizable. So, again inconsistency.
3. User can rename folders, so we'd need some more code to handle that properly for addressbooks and others (and e.g. implement use of the "show original folder names" preference).

So, I think that's why we do not localize the default contacts folder. Too much effort, but of course you can open a ticket to re-consider.

Kolab addressbooks are just folders, so users can rename them by themselves. It's also possible to have the folders in German by default on your own Kolab installation. We however do not have localization-dependent name for the "Contacts" folder.

Yes. It uses IMAP \Flagged flag. This is the same as "Starred" in Thunderbird.

@bohlender, I would need first test if the plugin works with Elastic skin. It probably would, as its author is quite active. Yes. create a bifrost ticket, please.

Please, note that there exists contextmenu plugin, not enabled on your demo. It would fix it by enabling right-click menu on the message record. Also, note that on desktop we have drag-n-drop functionality implemented, so you can drag and drop the message to Trash folder (use Shift key on drip to select from copy and move actions).

What device and browser version?

Could we just set content-length header using 4th argument of the client->request() method? I mean use the header for both operation modes, i.e. for file as a stream and as a string. These curl settings look very hackish.

I didn't read curl sources, but maybe Sabre/HTTP/Client should define CURLOPT_READFUNCTION.

I'm telling you Sabre supports file handles (https://github.com/sabre-io/http/blob/master/lib/Client.php#L397). Problem is that for some reason the handle is not seekable, which is a requirement from curl. From what I know rewind is needed in case of connection redirect or interruption, but anyway I don't see why it couldn't rewind.

Sabre (and cURL) supports the body as a resource. So, the bug is somewhere else.