Why 1password does not work correctly with subdomains?

Another +1 for this feature.

My $0.02 is that this should be a vault level setting. Basically "enforce strict subdomain matching" which can be off by default so the app retains the behavior it has today. Then, if we check that box, we have to add all the domains and subdomains to the login itself.

This also solves Ben's issue from the iOS thread about this about not breaking Google suite; the app would work the exact same way it does now unless you check the box. A simple dialog to inform the user of the "extra" work that will be required if enabled and then boom, everyone is happy.

With all the focus on Developers and integrations, this absolutely needs to be a priority. Devs themselves may be a small minority of the user base, but they are also the ones who are going to convince families (and even companies) to even bother with a password management tool.

Not to mention all your competitors can already do this.