If, for example, I go to Amazon and create a new login item, if I don’t rename it myself, it will be listed under W because it’s named www.amazon.com by default. This can be frustrating for less experienced users.
Why not just call it amazon.com, so it will sort where most users would expect to find it?
And why not pick just Amazon?
It does make sense to use amazon.com by default when creating the entry, presuming the user has not changed the default match detection. Since www.amazon.com, login.amazon.com and amazon.com will all match the entry, a name like “amazon.com” accurately reflects what it will match.
The root domain (.com) is important because it disambiguates. If somebody else were to own Amazon.org, it would not be helpful for the name to look like it would match.
This used to be the original behavior, but it was modified to use the FQDN as the title in 2018, in response to a feature request:
Best solution may be to make this an optional feature, or perhaps to use the default URI match detection rule as a guide for how much of the URL to keep as the login title.
P.S. I changed the topic’s “app” tag from “app:all” to “app:browser”.
I agree that it should be an option of some kind. It could be just a check box to use the Default URI match detection for object naming. But for me it would help if “www” specifically was stripped as “www” is always redundant.