Closed r-a-y closed 7 years ago
I have to agree the site aliasing feature is really confusing at the moment. I had to go and read your blog post before I could understand what was happening. Perhaps instead of improving the documentation we should figure out a way it can work that's less confusing?
Perhaps there should be a button "This domain is an alias" or something like that? When clicked it could prompt the user to type the alias domain. Maybe we could only display that button when the current domain doesn't already have any (non legacy) passwords?
Since LastPass offers a search bar at the top of the popup panel which allows the user to search for other domains, perhaps we should do something similar? When I first saw the edit button next to the current domain that's what I was expecting it to do; provide a way to view passwords for a different domain. If I'm currently browsing GitHub I might still want to view my passwords for PayPal, it doesn't mean I want to alias the two domains.
I agree, aliasing functionality should simply me more obvious - I changed the title of this issue to reflect this. Here is what I have so far:
This clearly separates the two scenarios: website without passwords (adding an alias) and special page (no site is set), different message is shown for those. Websites with existing passwords won't show any link.
I'll change the display for aliased websites soon.
These messages seem to be good enough now:
This way it should hopefully be obvious enough.
Yea, way clearer now :+1:
I had a hard time trying to figure out how to use this feature, since I couldn't find any documentation about this.
After some trial-and-error, here are some quick instructions:
example.com
, and you land on a subdomain such asa.example.com
and share the same login credentials as the main site, you should edit the website name froma.example.com
toexample.com
.Hope that helps.
Thanks for creating this project, @palant!