Note that there are some explanatory texts on larger screens.

plurals
  1. POIntercept unused tap events in a UIWebView
    primarykey
    data
    text
    <p>I'm working on an iPad app which is based on a UIWebView: to explain it in the simplest possible terms, the app shows one big interactive webview and in addition it supports custom gestures.</p> <p>I need to catch events that represent single taps on the webview, but only when the taps have not already been consumed by the webview (i.e. they are not the beginning of a scroll/zoom operation, they are not taps on links, they are not taps that trigger some javascript).</p> <p>The UIWebView is very greedy with its events, and in my experience it tends not to propagate them, even when they are not consumed. To catch the events, I ended up subclassing the main UIWindow (see <a href="http://mithin.in/2009/08/26/detecting-taps-and-events-on-uiwebview-the-right-way/" rel="nofollow">http://mithin.in/2009/08/26/detecting-taps-and-events-on-uiwebview-the-right-way/</a>). This is working well, but the problem is I'm not able to recognize whether the taps I'm getting have triggered some javascript in the webview or not.</p> <p>As an additional restriction, I have no control over the javascript that's going to run in the UIWebView or the HTML that it's going to be displayed.</p> <p>So, the question goes like this: what would be a way to detect all and only the tap events which did not trigger any other action in the UIWebView itself, especially javascript actions?</p> <p>~</p> <p>Should you be curious, the source code of the project I'm working on is on GitHub: to find it, just ask Google to point you to Baker Framework.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload