Forum Discussion

Former Member's avatar
Former Member
4 years ago

80600068 BETA - No longer works with touch UI

Using 80600068 BETA on a Surface laptop 5, most of the program's UI no longer responds to touch screen (including with the pen) input. The leftmost region (with vault selection, categories etc) still responds to touch and I can move the window and using the 3 dots menu using touch from this region. However everything else does not respond to touch. I can't select an item, minimize, maximize or close the window. While I can call up the setup window with touch, the entire window doesn't respond at all.

1Password Version: 80600068
Extension Version: Not Provided
OS Version: Windows 10

betas

6 Replies

  • martinsteel's avatar
    martinsteel
    Frequent Contributor
    3 years ago

    Hiya @"ali.hazime" touch does indeed work with beta 8.7.0. 👍

  • AliH1P's avatar
    AliH1P
    Icon for 1Password Team rank1Password Team
    3 years ago

    Hey @DrRZ and martinsteel, I just wanted to let you know a fix has been implemented for this issue in the latest Beta. If you're currently on the Beta channel, let me know if you run into any further issues with touch input. Otherwise, if you'd like to switch to the Beta release, you can follow these steps. Thanks!

    Ali

  • Mathieu_1P's avatar
    Mathieu_1P
    Icon for 1Password Team rank1Password Team
    4 years ago

    I'm very sorry you are experiencing trouble with touch interactions. We have been able to reproduce this issue internally and are investigating the best way to resolve it. In the meantime, the mouse continues to work on touch based systems if you have one available to you.

  • martinsteel's avatar
    martinsteel
    Frequent Contributor
    4 years ago

    Unfortunately this broken beta was promoted to live so touch is now completely unusable in 1password 8 :(

  • 1P_PeterG's avatar
    1P_PeterG
    Icon for Community Manager rankCommunity Manager
    4 years ago

    Hello @DrRZ, sorry to hear of this trouble. I have passed on this information so that we can test this out internally and see if we can better understand the issue you describe. Thank you for alerting us to the issue!

    ref: dev/core/core#13577