Jun 5, 2018 marco @1Password Just double checked with 0.4 - it seems to be fixed now. ← Previous Next →