On 20 Oct 2014, at 17:21, Håkon Alstadheim <hakon@alstadheim.priv.no> wrote:

On 20. okt. 2014 16:21, Ján Máté wrote:

Hi Håkon,

this is not a bug, it is a feature - the username/password "save" functionality is explicitly disabled in the source code.

Ah. OK .

We will add a configuration option to disable this functionality in future.

Temporarily you can remove the
autocomplete="off"
string from the index.html (present 2x) and then execute the cache_update.sh

Did that now, but I'm not all there yet. Tried first setting them from "off" to "on", and that made Chrome save the password (I /think/ if it was not already there), but still showed me the login dialog on a page reload.

support for storing password is a browser functionality, but not showing the login page is NOT browser functionality. Cal/CardDAV usually use basic (or digest) authentication and no session cookie (or anything similar) which is usually used for "remember me" functionality (your browser sends the authorization cookie to the server, so it looks like you are automatically "logged in" without any login screen). There is no way to achieve this functionality with basic/digest auth.

Lots of things cause a page reload, so it is kind of important to get to the bottom of this :/ . (I did run the script and reload apache for good measure. No joy. Tried several times).

Removing the setting entirely, removing the saved passwords in chrome and rerunning the script, restarting apache makes the passwords not even show up in "saved passwords" in chrome.

Reverting to autocomplete="on" gives still no joy, password not even saved anymore. I'm starting to think I had those passwords stored from before, when I was trying various things to get this working, like temporarily disabling javascript.

How many people are using CalDavZap with ChromeOS? (HP-chromebook 14, Norwegian locale, a few "childhood diseases" are still not over).