lkhrs

The beta version of 1Password's Chrome and Firefox extensions (2.4.2 and 2.4.3 respectively) are working better for me than the current stable extension, but there's still some issues. Biometrics not working is one thing and depends on AgileBits whitelisting Orion, but the other issues (blank popup) and Chromium working fine (minus biometrics) make me think there's some extension API issues in Orion that might be worth another look by the team.

Things I can do that I couldn't do in the stable version:

• Log in to the extension (was hit or miss in stable)
• Autofill suggestions show up below form fields
• The extension popup menu shows up
• Save passwords

Issues:

• Two-factor auth cannot be filled from the autofill suggestions, you need to copy it directly from the extension toolbar popup or from the app

• Clicking the 1Password icon in a form field throws the "Collect Frame" promise warning noted below

• If app integration is turned on in settings, there's a 5 second delay before the popup shows up

• Sometimes the popup will just be blank, with no loading indicator, and the following warnings get logged to the console:
  
  Turning off app integration in the 1Password extension settings and restarting Orion reduces the delay and gets rid of the browser verification error (of course).

• When the extension periodically locks (seems to ignore the 10 minutes setting), you'll need to enter your password. After unlocking the extension, I get a blank popup with no loading indicator regardless of the app integration setting. Going by the console log, it appears the extension unlocked successfully and loaded a page after 5 seconds, but the popup is blank.

Console from the web inspector in the popup:

When the blank popup after unlock issue happens, the only workaround is to restart Orion. Reloading or disabling/enabling the extension had no effect, the password field still appears to unlock the extension, followed by a blank page after unlock.

From my testing, it appears Chromium itself isn't whitelisted by 1Password either, since biometrics don't work. Using the extension results in no errors and everything works as it should, which is why I think there's an extension API issue happening.

I'm struggling to think of a solution that wouldn't look cluttered or ugly. If we indent the favicons the sidebar could probably get to 3 levels until we'd have to stop showing hierarchy due to space.

Another solution would be to take the vertical left-side line idea and add a parallel line per level.

I don't think either solution would look good though.

Hi Vlad,

I like your mockup of a kanban system for browser tabs! While I agree with you that thumbnails are complex, I rely on them to tell the difference between identical sites, like different pages on the same documentation site, or WordPress dashboards for multiple sites (I color my WP dashboards differently per site).

However, I don't think thumbnails need to be as large as they are in Safari's tab overview—I think a good compromise would be to have tiny thumbnails to the left of the tab cards:

I can't remember where I saw this thumbnail design, where the image is cropped around the logo area. Maybe it was the Speed Dial thumbnails in old Opera, before they switched from Presto to Chromium (RIP).

Arc's design looks like they're optimizing for tap targets, but Arc is a browser for macOS, so it doesn't make much sense to waste space like that. I think the overall idea is to browse with purpose rather than tab hoard, and maybe bigger UI elements encourages less open tabs. The tab auto-archive feature helps with tab clutter. I'm not a fan of the approach though.

I love it when apps have a command palette, and I think showing it instead of a new tab page is brilliant! My new tab page is blank in all my browsers, because it's too easy for me to get sidetracked by bookmarks, frequently visited, reading list, etc. Would love to see a command palette in Orion in the future, even if it doesn't replace the new tab page.

Also, I'm a fan of your work, I've been using your wallpapers since 2011.