Keeweb: Global shortcut for Auto-type

[loilo]

I just checked 1.2 and Auto-type (the most longed-for feature for me) works great. It would actually be nice if there would be the chance do define a global keyboard shortcut to use Auto-type. It's what really makes KeePass fast and easy to use everywhere.

I know we had a short discussion about detecting programs/URLs for Auto-type usage in the original issue. Did that feature just not make it into the release or has it been abandoned entirely?

(And thanks for the great work with 1.2 again!)

[antelle]

Hello,
This will be implemented in v1.3, and it's already done partly.
I planned to include it in v1.2 release before but unfortunately, I hadn't enough time. So I decided to release v1.2 faster and improve auto-type later in v1.3.

[loilo]

That's amazing news, thanks. :)

[benzkji]

Hi, just to clear things up (forgive me if I mix and match or whatever, just downloaded keeweb): Autotype with system wide keyboard shortcut is not implemented in 1.2, but will be in 1.3 (as described here: https://github.com/keeweb/keeweb/wiki/Auto-Type).

There is a cmd-T shortcut (when in keeweb), but it just opens Safari with my homepage? What was this intended to do?

Copying data from keeweb when it's in background works perfect, btw...thanks for your great work!

[antelle]

Global shortcut will be Ctrl+Alt+T on mac and Shift+Alt+T on other os.

[antelle]

Status update: global shortcuts for auto-type have been implemented, v1.3 will have it. If the app was locked, there will be unlock window, after which entry list will pop up.

[loilo]

That will be an amazing improvement. :)
It also indicates though that any kind of automatic selection of an entry (after the global shortcut) will not be in 1.3, right?

[antelle]

automatic selection of an entry

what do you mean?

[loilo]

Sorry, I'm repeatedly referring to KeePass without mentioning it.
KeePass' AutoType allows to assign Entries to programs (via their title if I'm not mistaken) resp. if no assignments are made it matches the entry data against the currently focused window's title to pick the right entry without even having to ask the user.

Since there already was some discussion about how to detect URLs I assume that some kind of feature in that direction is planned, but your announcement sounds like for 1.3 there's no implementation of this idea and the global shortcut rather shows a list of all KeeWeb entries.

[antelle]

It works in this way: it tries to find matching entries by url and title. If there are no (or more than one) matching entries, show entry selection window, with entries sorted by best match (more details about sorting and filtering). If exactly one entry has been found, there will be no selection window. I'm thinking about 'I'm feeling lucky' setting which will always select the best match, we'll see if we need it, I don't know for now.

[loilo]

Wow - sounds great that this will already be implemented. 👍

[antelle]

Auto-type is finished for v1.3.
If you would like to test it, please let me know, I'll make a beta build.

[loilo]

I'd love to test it on my Windows machine.

[antelle]

Here's the beta: http://antelle.net/files/KeeWeb-1.2.4-beta.win.x64.zip

[pwFoo]

I have some problems with the entry detection. Entry isn't identified by title or url an suggestions seems to start with "a" instead of best hit (maching title or url).
But I'll do some more testing :+1:

[antelle]

@pwFoo you can look in log, to check the reason of this. most probably url was not detected

[pwFoo]

Yes, thanks. Your right.

I think You should ignore url parameters like ?return=%2F (referer page for example) and browser title extensions like - Google Chrome.
Could you add domain match instead of full url only? And a partial title match (because browser add the browser name string...).

[antelle]

It's already matching by domain.
Please write here:

• tab url (as returned to keeweb. from dev console)
• tab title (as returned to keeweb. from dev console)
• entry url (which you expect to be matched)
• entry title (which you expect to be matched)

[pwFoo]

No selection window / match with the downloaded beta package. No action with global auto type. Changed inside the app to dev / beta version and there is a auto type action, but without matching entry, just a manual select list.

No url field (domain only, proto + domain and full domain with path / params) or title match. Verified browser and entry title is the same. Strange... Tested with Chrome @ Windows 10.

[loilo]

I'm testing the Beta you posted for Windows right now. Auto Type works kind of, but the Detection of the URL (which worked fine on OS X) does not. The app does not even seem to try:

2016-08-11T20:58:44.951Z [auto-type] Auto type event null
2016-08-11T20:58:44.953Z [auto-type] Get window title
2016-08-11T20:58:45.565Z [launcher] spawn C:\Program Files\KeeWebresources\app\helper\win32\KeeWebHelper.exe: 0, 613ms
GMX: Email-Adresse, FreeMail, De-Mail & Nachrichten – Opera
https://www.gmx.net/
2016-08-11T20:58:45.566Z [auto-type] Window title GMX: Email-Adresse, FreeMail, De-Mail & Nachrichten – Opera https://www.gmx.net/

[antelle]

Hm, what in the log you posted above makes you think that the app does not try to detect url?
I see that the url is detected ok, which is gmx.net.
Or you mean, it detects url and after it, no auto-type is performed? What's going on in the log after 'Window title:' record?

[loilo]

...obviously seeing the literal URL printed out didn't prevent me from thinking it was not detected. Meh. I'm probably to tired to write bug reports. :)
The logs are complete, no other ones are shown and the App will tell me that there are no matches (though there clearly are).

[antelle]

So, the url and title were both detected in your case (otherwise they wouldn't have appeared in keeweb logs). Are you viewing logs from dev console or from app Settings/Advanced? Dev console can sometimes have errors which are absent in Settings/Advanced, maybe it's your case.
Hmmm, that's really strange that Window title is the last record, could you please paste title and url of the entry which should have been matched by these parameters? I'll check calculated rank value for this entry. Something definitely went wrong here.

[loilo]

I view the logs in dev tools. I just took a look into Settings/Advanced logs as well (after changing the app theme since in "White" theme logs are unreadable due to a really light font color) and they don't tell anything the dev tools wouldn't.

The entry's title is "GMX", its URL is "gmx.net". It does not matter too much though since the issue happens with every single webpage I visit (also in any Browser) with the same kind of logs.

Just to add that, I'm on Windows 10 (installed Anniversary Update) and used the .zip file from above.

(btw it would be great if you could provide another zip with the fixed #308 since that would allow for much further Auto Type testing :+1:)

[benzkji]

how can I test auto type on mac? do you need to make a MAC build? @antelle

[antelle]

Uploaded new beta build for windows and mac.

[benzkji]

I cannot open Files from Dropbox in the Beta build, if I click the Icon, it turns, and nothing happens. Is this because the "AppId" (or whatever it is called, dont know the Dropbox API) has changed for beta, or a regression?

[benzkji]

And thanks, will test with a local file anyway !

[pwFoo]

Tested latest beta build. It triggers auto type, but it doesn't fill the form inside the active browser window. Instead KeeWeb will be maximized (from minimized / background) and the website passwpord is filled in the KeeWeb search field.
auto type shouldn't change the window focus ;)

[antelle]

KeeWeb will be maximized

It is maximized when it shows entry selection dialog, not when there's one matching entry. Is it different for you?

[antelle]

Oh yes, this appeared in last beta, fixed wrong window focus, uploaded new beta build.
We have to create a beta channel... it's hard to download and update them manually.

[pwFoo]

No selection dialog. App gets maximized and matching entry is filled in the KeeWeb search field instead of the browser / form.

Beta channel is a good idea!

[antelle]

Yes, thanks for that, I've found the reason and fixed, new beta doesn't have this bug.

[pwFoo]

Great! All will test it as soon as the new beta is available :)

[antelle]

It's already deployed

[pwFoo]

Auto type works fine on Win10 with the latest beta! :+1:

[pwFoo]

auto type entry detection based on domain works fine, but it looks like title doesn't work?

[antelle]

Please paste window title and url (from keeweb logs, starting with [auto-type] Window title) and entry title and url.
A simple case works: e.g. when I'm in a text editor titled Untitled, and there's and entry Untitled, it's matched.

[pwFoo]

Browser title bar: "My Domain Title"
KeeWeb detects: "My Domain Title - Google Chrome"

Could "[...] - Google Chrome" a problem to match an entry?

I have a entry with changed domain. Old domain redirects to the new one. So no domain match is possible.
So it should match title "DSA-Forum" I think...
DSA-Forum • Persönlicher Bereich • Anmelden - Google Chrome www.dsaforum.de/ucp.php?mode=login [DEBUG] 2016-08-14T11:26:56.665Z [auto-type] Window title DSA-Forum • Persönlicher Bereich • Anmelden - Google Chrome www.dsaforum.de/ucp.php?mode=login

I get an empty selection window instead of the matching one.
Changed the domain (dsa4forum.de) match the new domain name (dsaforum.de) and auto type works again.

So it should by a problem with title match?

[antelle]

I have a entry with changed domain.

Yes, this is by design. If you just remove entry url, it will match. If we can detect the url and domain in entry and this url mismatch, we think that it would be potentially dangerous to perform auto-type for such entry automatically. To enable auto-type for this entry on this domain, add url into any entry field. For example, you can add a field 'Another url' and fill it with login url.

[pwFoo]

Hm, you're right! It's dangerous to perform auto type for such a entry...
Domain match should be fine for most cases.

It isn't a bug it's a (security) feature!!!

Thanks!

[loilo]

Okay, this also solved my problem of not finding matching entries. I used "gmx.net" in the "Website" field but it actually was "www.gmx.net".
While I actually agree with the security feature you mentioned, wouldn't it be worth thinking about an exception for www aliases?

[antelle]

Yes, sure we must add an exception for www.
Added, deployed to beta. If you click use beta for one time button in beta build, it should work.

[loilo]

Works like a charm. :+1:

[antelle]

@benzkji
I cannot open Files from Dropbox in the Beta build

Fixed it, Dropbox is working in latest beta.

[rholloway]

For me when trying beta I get 'helper not found' when I run auto type. Not sure what is going on there.

[antelle]

It requires native helper, so Beta button won't work. Latest beta: mac, win.

[Tephnos]

Hi. Saw this recently when looking for a new app to replace 1Pass, and having been used to 1Password's autofill, I noticed on KeeWeb that if you're on the right page, you need to have the login box highlighted first, or nothing will happen (or click some random thing).

Is this normal Keepass auto type behaviour? Presuming in order to 'locate' the correct boxes for password entry it would probably require a browser extension? Just making sure that's normal behaviour and not something amiss.

[antelle]

Yes, login box must have focus, it's not searched automatically.

[antelle]

Why do you post it here? Everything subscribed to this issue will be notified about your comments.

1. will be deleted automatically, when the icon is not used
2. but it's not inserted automatically, it's just a hint. also, it will disappear once you start typing. It should not be annoying.