This is what's keeping me from switching from Bitwarden right now. Crucial for self-hosting when you have several logins at the same domain but at different ports.

If you self-host some stuff this is crucial!

Please! I have many services run locally at my home on different ports

I have different services on their own subdomains and each have their own logins. But when I try to login to sub1.domain.com it suggests logins for sub2.domain.com, sub3.domain.com, and sub4.domain.com. But the browser plugin only shows two suggested logins and how often do you think it’s the right one?

Good to see I am not alone, can't use Proton Pass without this basic functionality. Have mentioned it in every feedback/survey, in some forums, but been waiting since first launch for it to get implemented, quite ridiculous it's still not done while other less important stuff (admittedly that's subjective) has been added already. Sticking to Bitwarden like many others.

This is the configuration that keeps me in Bitwarden for the moment

This is a feature I can't live without. This is one of the main reasons I can't use Proton Pass as my main password manager.

I forgot about how incredibly useful this feature in Bitwarden is ... until I started testing Proton pass.

First internal site I wanted to login to had over 30 matches.

The next page I logged into is this one here to vote for this feature.

This feature is critical for me for business uses; and has been a massive pain point since trying to move from BitWarden. Many of our internal systems are under the same domain:

customer1-release.company.com
customer1-develop.company.com
customer2-release.company.com
customer2-develop.company.com

etc.

This often results in the situation that autofill is completely *useless* for anything related to our business. It also inevitably results in many 'Do you want to update this password?' messages that are completely unrelated to the active website.

Subpath recognition would be awesome

The inability to distinguish logins across subdomains is a significant roadblock to adoption. Frankly, a little surprised this product went GA without that functionality considering it's prevalance as a standard feature for like products.

different subdomains should never have been treated as being the same application to begin with. the complex rules described in the original post could be optional to keep things simple imo.

Critical feature for me, as someone with a lot of services under the same domain

+1 Essential feature for me to switch!

Is this on the roadmap yet?
Where is the a roadmap published?

+1, this is extremely important. I have 35 services running under my local domain and Proton Pass is currently showing all entries for all services

This is a critical feature IMO. Please implement it. I'm surprised it wasn't implemented from the beginning to be honest.

Definitely waiting for this!

Also, when added, make sure to have an indication on the field that URL match detection has been changed from the default match detection.

As a member of the self-hosted community, this is a critical feature. I have dozens of services sharing the same base domains.

I like Bitwarden's approach to the problem: https://bitwarden.com/help/uri-match-detection/

Adding this feature will allow me to fully adopt ProtonPass as my primary password manager of choice.

the minimum, filtering by host : aaa.domain.com / bbb.domain.com...