Since the last update, opening the browser extension produces a long list of logins.

@grumpy21: Forgive me for asking, but I just want to make sure I understand correctly: Are you saying that, when you have no URL open in your browser, 1Password shows you a list of Login items without URLs? If so, it sounds to me like 1Password is matching the URL in these cases just as it would normally match the "website" field to the website you're visiting in others — there's just isn't one. That actually doesn't surprise me, though I admit is isn't something I'd ever bothered to consider before. Sailing past the part where you have a bunch of Logins without URLs in the first place (I'm not sure I understand that), can you tell us a bit more about your setup? Which browser version are you using, for example?

@grumpy21: Thanks for getting back to me! I have to say, I'm not convinced that something's changed on the Mac. Both Mac and Windows versions use the same extensions, and frankly we haven't shipped an update to the Mac version recently either.

This is very intriguing though, and in my experimentation I think I may have narrowed it down a bit. I actually have at least one login I just created for testing this, and it doesn’t show up on about:blank. However, I do have 4 other logins show up there as matches, with various URLs: file:/// , Unicode characters, etc.

But I guess what I'd really like to know isn't why yo'd want some logins without URLs — I think we all have some of those, and you offered a pretty good example (though I prefer to use multiple URLs in most cases like that) — but rather how or why you've seemingly created logins with blank "website" fields in the first place. If I create a new login and don't enter a URL, it isn't saved without a "website" field entirely, and in this case it doesn't show up as a match for about:blank. Only if I enter something (a "space", for example) in the "website" field and save it does the field exist in the item and therefore present as a match. So it seems that the extension treats any URLs it simply doesn’t understand as matches for about:blank, perhaps because it doesn’t understand that URL either. :lol:

This is definitely a bit of an edge case because of this, so I'm interested more in figure out how you got into this situation and figuring out workaround that works better for you than changing your startup page, etc. Can I make a suggestion? When you mention bookmarks, this is really how I use 1Password much of the time myself, albeit in a slightly different way, so maybe I can offer some help. I find that having URLs in my logins makes using 1Password as a sort of bookmarks repository much more useful, since I can just hit ⌘ ⌥ \ (Command Option \ — or Ctrl Alt \ on Windows) and either select a login manually through the menus (nice) or by searching (even nicer) to have 1Password open the page and fill there.

There's a lot here, so let me know what you think. :)

@grumpy21: Ah, we'll if we're talking 2 or 3 months, that certainly changes things, as we have released updates in that time frame across both the extensions and apps. Thank you for the illustration, and for confirming that imported data may be involved. I feel like right now your best options will be search (since that will easily clear the matched list and get you the "bookmark" you want) or removing the errant "URLs" from some items.

We've been discussing this internally, and the short version is that while this isn't a specific use case 1Password is trying to accommodate, there are definitely improvements we'd like to make to URL handling in general that would help in your case as well. That bad news is that this will be a long-term thing since it will involve changes across multiple platforms for both the apps and extensions. In my comments above you can get a hint about this where I talk about Unicode and file:// URLs. 1Password should be better at parsing URLs in general, so this is an area we'll be working on in the future. I'm sorry I don't have a better answer for you right now, but I'm really glad you brought this up as it's something we can be aware of as we improve 1Password's URL handling. Cheers!

Hi @grumpy21,

Over the years 1Password has definitely improved because either people have been passionate about wanting 1Password to be capable of something in particular or come to ask us a question. So we're just as glad when people come to ask us "why?" and we discover something that was overlooked. Even during the brief period I've been with AgileBits I've seen it help mould 1Password and make it a better product in large and small ways. Thank you :smile: