Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
martinsteel
4 years agoFrequent Contributor
Touch input incorrect with 1p8 on Windows 11
1password 8 doesn't seem to work correctly with touch input, version 7 was fine.
Context menus appear in the wrong location on screen, generally lower and up to 10-50% of the screen width to the right.
Some touch events are completely ignored e.g. the save button won't do anything but tabbing to it works.
No way to multi-select items with touch
1Password Version: 8.4.1
Extension Version: Not Provided
OS Version: Windows 11
Referrer: forum-search:https://1password.community/search?Search=touch
19 Replies
- ag_mike_d
1Password Team
Hello again martinsteel,
Thanks for passing along these details for each use case. As I do not have Windows touch device, I've been unable to test. I'll update the team with details the details provided. I don't have further news to share at this time, but we'll be in touch when we do. We appreciate your patience!
ref: dev/core/core#11876
- martinsteelFrequent Contributor
Hiya ag_mike_d
Both with and without mouse appear to be wrong still.
With mouse:
The context menu appears at the mouse pointer rather than the touch point, that's the bit that's very confusing if you have multiple monitors.Without mouse:
Context menu appears centred on the monitor (looks like top left corner is dead centre of screen). Doesn't matter if focus is on a textbox within 1Password or another app.Expected behaviour:
Context menu appears at the touch point so that it's convenient to then touch and select something, this is what every other app, and Windows itself, does on Windows. - ag_mike_d
1Password Team
Hello martinsteel,
Thanks so much for your message. I'm sorry to hear you are still having some issues with the context menus on touch devices.
It sounds like you may be referring to the device where you did not have a mouse. Is this still the case? As previously mentioned, the context menu should be appearing next to the cursor, and not where you are tapping. If your tap the search bar for example, to move the cursor there, does long pressing cause the context menu to appear at that location? Could please let us know if this works or does the context menu continue to appear in other odd locations?
Then, if you tap a item from the list to highlight it and then long press, what behaviour do you see from the context menu and where does it appear?
Looking forward to your reply.
ref: dev/core/core#11876
- martinsteelFrequent Contributor
ag_mike_d context menus are still broken on touch devices 10 months later.
- ag_mike_d
1Password Team
Thanks, martinsteel - Do let us know if you get a chance.
- martinsteelFrequent Contributor
ag_mike_d I missed your reply so sorry for the delay.
That agrees with what I'm seeing now, slightly confusing when the cursor is on a different monitor :)
I was seeing this on a touch device without a mouse (so no on screen cursor) but don't currently have access to test and confirm. I'll let you now if I get a chance.
- ag_mike_d
1Password Team
Hello again, martinsteel! I'm glad things are working better for you.
With regard to the context menu and based on some details I've read in our filed issue, I understand that the context menu is appearing next to the cursor, and not where you are tapping. Can you confirm if this is the case or if you're seeing something different? In the meantime the team will continue to make improvements as needed with the touch interface on these types of devices.
Thanks for this additional feedback and have a great day!
ref: dev/core/core#11876
- martinsteelFrequent Contributor
ag_mike_d first impressions with 8.7 beta seem good. The various touch issues seem to be fixed, except context menus - they still appear in odd locations but that's a minor niggle rather than a problem🙂
- ag_mike_d
1Password Team
Thanks for the update, martinsteel! The team is continuing to investigate and we'll be in touch when we have more to share!
- martinsteelFrequent Contributor
ag_mike_d just to let you know still seeing this in 8.6.1