When trying to tap + hold on a link with -webkit-touch-callout applied, the adjacent link is triggered unexpectedly
Reported by
ch...@xenforo.com,
Feb 22 2018
|
||||||||
Issue descriptionSteps to reproduce the problem: 1. Test using the attached HTML file 2. There are two links. 3. First link has a URL of #SMILE and it has -webkit-touch-callout set to none. 4. Second link is normal and has a URL of #NORMAL_LINK 5. If you tap and hold the #SMILE link centrally, nothing happens (as expected) 6. If you tap and hold the link towards the right side of it, often the #NORMAL_LINK touch-callout is activated. What is the expected behavior? While tapping and holding on any part of the #SMILE link, nothing should happen. What went wrong? While tapping and holding towards the right hand side of the #SMILE link, somehow the #NORMAL_LINK touch callout gets activated. This can be verified in the header of the "Open in new tab" menu that comes up. Did this work before? N/A Chrome version: 64.0.3282.112 Channel: stable OS Version: 11.3 Beta 3 Flash Version: You can also see from the attached video what happens. In Safari, it works as expected. Even if you tap and hold as close to the right hand side of the element as possible, while the SMILE link is tapped on (which you can see from the shading around the element when it is touched) nothing happens. In Chrome, you can clearly see that the tap is on the SMILE link (again, from the shading around the element when it is tapped) but the touch callout menu that comes up (which shouldn't come up because of -webkit-touch-callout) suggests that the adjacent NORMAL_LINK link was tapped instead.
,
Feb 22 2018
Seems like a web compat issue, danyao@ can you take a look?
,
May 11 2018
Hello, I appreciated how quickly this was assigned to someone, though I'm somewhat disappointed at the amount of time now passed without a response. Do we know when someone might have a chance to look and comment on this? Many thanks
,
May 15 2018
Sorry about the delay. Vanilla WKWebView behaves the same as Safari. So I suspect the issue is related to Chrome's custom getElementFromPoint: https://cs.chromium.org/chromium/src/ios/web/web_state/ui/crw_context_menu_controller.mm?q=getElementFromPoint+file:ios/web+-file:test&dr=C&l=473 Unfortunately I won't have time to work on this any time soon. Adding this to list of issues caused by injected JavaScript.
,
May 15 2018
Thanks for the update :) Can you recommend any CSS based workaround that we might be able to implement? I appreciate that's not necessarily an easy answer... Thanks
,
May 25 2018
,
Aug 2
,
Oct 18
This is a bug in context meny. Mike, can you take a look?
,
Oct 26
,
Oct 26
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ch...@xenforo.com
, Feb 22 20181.5 MB
1.5 MB View Download