Drag-and-drop spring-loaded targets lack learnability indicator

Originator:zach
Number:rdar://32997176 Date Originated:June 27 2017, 12:07 AM
Status:Closed Resolved:true
Product:iOS + SDK Product Version:11.0 Beta 2 (15A5304i)
Classification:UI/Usability Reproducible:Sometimes
 
Area:
Something not on this list

Summary:
Drag-and-drop provides a new way to open tabs. It's not perfect.

This radar chain (see also: <rdar://problem/32996994>, <rdar://problem/32997088>) centers around a reasonably common action for me while reading on iPad: I open a web-page, such as a link-heavy article, and spawn many many links from the page in tabs. The overall experience has regressed in iOS 11 beta.

I explore in <rdar://problem/32997088> that retaining the Safari long-press menu for links and images is sub-optimal when drags preempt them, necessitating that I wait longer. After struggling with this for a few minutes, I eventually found that the New Tab toolbar item is spring-loaded. This was completely un-discoverable.

Steps to Reproduce:
1. I open a webpage.
2. I want to open links from the webpage.
3. I tap-and-hold on the link

Expected Results:
I can open multiple tabs quickly.

Observed Results:
I must wait for a drag to engage before the long-press even shows, then wait for it to end before tapping in the action sheet. This process is noticeably longer than iOS 10 and still way way way longer than macOS.

Version:
11.0 Beta 2 (15A5304i)

Notes:
Possibility: by default or through an accessibility setting, the system indexes views that have added a spring-loading interaction or have activated an SDK-provided one.

Configuration:
iPad Pro 10.5”, 1st generation

Comments

Radars referenced:

http://www.openradar.me/radar?id=5042055197753344 http://www.openradar.me/radar?id=4994347640553472


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!