BUG: Still can't auto fill apps from quick access in Windows

...Continued from previous comment due to character limit.

1. Open your phone to get your 2FA code because after the rigamarole above, there's no way you're delegating that responsibility to 1Password as well. It's quicker just to open the app on your phone and type in the number. Besides, I'm not even sure if quick access provides a way to copy 2FA codes. I don't see it in my quick access, but again I've never configured TOTP for any of my credentials in 1Password so it may just be omitted because I don't have it. I did do a quick google search for "1password quick access 2fa" and didn't see any mention of it being available from quick access and none of the screenshots that came up had it either. Are you able to confirm whether or not this works? And if so, what is the keyboard shortcut to copy a 2FA code from quick access? You seem to have left it off your list of "Ctrl + Shift + Space shortcut to open Quick Access, followed by the Ctrl + C shortcut to copy your username or the Ctrl + Shift + C shortcut to copy your password" so it's not clear whether it's just not possible through quick access or if you forgot to include it.

So just to get this on the record, the above workflow is the "intended" usage of quick access (complete with all the keyboard shortcuts which AgileBits is always so quick to helpfully suggest to streamline and speed up the process) correct?

I don't know about you but this doesn't seem very quick to me. I can see how the feature might be quick for the developers who built the thing around their own personal needs, hardware setups and use cases (and the customers who just so happen to match those same circumstances). Presumably they are on MacOS where auto-fill functionality and associating passwords with apps mostly works as expected and they don't need to search for their credentials every time or manually copy/paste credentials. Maybe they are also on machines with biometric unlock features enabled or have their app set to never lock so they don't need to type their master password every time. Maybe they are using keyboards where the arrow keys are easily accessible rather than a laptop keyboard or 60% design where the arrows are a lot less convenient. Either way, it's unreasonable to expect that your paying customers are all having the same experience you are, and in my opinion it's rather condescending to be so dismissive of their experiences: "works fine for me, just use the shortcuts lol" (paraphrased) is not a very respectful nor professional answer when one of your customers is having problems.

Now let's compare the above process with simply using the full app:

1. Click the 1Password icon. No need to memorize any obscure keyboard shortcuts, just press on the little lock picture.
2. Enter master password to unlock the app.
3. Search for your credentials. Thankfully the full app provides multiple ways to make this step easier, such as different sorting options so recent/frequent credentials are displayed right there at the top of the list without even needing to type anything, or the favourites button to show the passwords you've personally configured to have quick and easy access to.
4. Select the credentials you want to use. In all fairness, trying to use the keyboard for this process is worse than quick access but using the mouse is a lot better.
5. Copy your username from the 1Password app to the app you're trying to log in to. Again, thankfully the app provides multiple ways to make this easier, such as providing the ability to simply drag and drop the username and password to where you want them with the mouse. It's also worth noting that those EXACT SAME KEYBOARD SHORTCUTS (which are apparently the backbone of what makes quick access so quick) are also available here along with all the other usability improvements. Again, credit where credit is due, quick access is slightly quicker at context switching back to the app because it automatically closes on copy (at the cost of having to reopen it to get the password afterwards).
   1. Paste username into the desired app if you didn't drag and drop it.
6. Copy password from the 1Password app to the app you're trying to log in to. We get to skip the second Ctrl + Shift + Space keyboard shortcut here because the app is still open so we can just grab the password directly.
   1. Paste password into the desired app if you didn't drag and drop it.
7. Close 1Password.

You can see how the full app is significantly quicker and easier to use than quick access right? I'm not imagining things or going crazy? Surely I'm not the only customer who feels this way.

Now, that said, there is a kind of middle ground here involving the "open in new window" feature which allows us to keep the password open without needing to re-summon quick access as well as giving the ability to drag and drop passwords, which at least saves us some of the effort by removing a few extraneous keyboard shortcuts. If we were able to swap that with "open in browser" as the default behaviour so pressing enter on a result gave us the new window and "open in browser" can be delegated to "ctrl/cmd + o" instead, that would go a huge way towards improving usability. Even better, if we could just get a search box in that "new window" to allow us to easily change which password is shown (or heck, even just allow an option for "open in new window" to reuse an existing "new window" if one exists if you're that intent on forcing us to use the inferior quick access) we could have something similar to 1Password mini back for users who prefer it with minimal effort on your part. All the pieces for it are already there in 1P8, they just aren't connected up to form a cohesive solution.

With that said, implementing an autofill feature that will work for applications is certainly something our team is interested in, but we don't have any plans or timeline to share at the moment. I'll pass your comment along to our product team to further highlight interest in this feature.

So implementing feature parity isn't even something you're working on at this time? Wasn't that the whole reason for switching to the electron based version with 1P8? Geeze, I'm glad I did make this bug report now. I always just sat back patiently waiting for the feature parity to come, assuming that since it was important enough to justify switching your entire technology stack with a ground up rebuild, and that this issue has been brought up multiple times, that it was something you were working on and hounding you about it was counterproductive. Again, you mostly have a working implementation in MacOS from what I've seen and again, the pieces are all there in Windows they just aren't wired up to quick access for some reason.

Continued in next comment (again) due to character limit...