Does UIGestureRecognizer work on a UIWebView?

Question

I am attempting to get a UIGestureRecognizer working with a UIWebview which is a subview of a UIScrollView. This sounds odd but when I have the numberOfTouchesRequired set to 2 the selector fires, but when numberOfTouchesRequired is set to one the selector doesn't fire.

Here is my code:

UITapGestureRecognizer *tap1 = [[UITapGestureRecognizer alloc] initWithTarget:self action:@selector(select1:)];
    tap1.numberOfTouchesRequired = 2;
    tap1.numberOfTapsRequired = 1;
    tap1.delegate = self;
    [self.ans1WebView addGestureRecognizer:tap1];
    [tap1 release];

- (void) select1:(UILongPressGestureRecognizer *)sender {
    //Do Stuff
}

I've confirmed this by using the Apple sample for UIGestureRecognizer and inserting a webview in their nib. Their tap code works everywhere but inside the area of the webview.

score 68 · Accepted Answer · edited Jun 15 '19 at 06:58

From what I have seen, UIWebView does not play well with others. For gesture recognizers, you could try returning YES from:

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldRecognizeSimultaneouslyWithGestureRecognizer:(UIGestureRecognizer *)otherGestureRecognizer;

I had to be backwards compatible with 3.0 so I ended up doing all the gesture handling with Javascript inside the UIWebView. Not a good solution, but it worked for my needs. I was able to capture a long press on an element, as well as tap, swipe, pinch and rotate. Of course, I was using only local content.

Edit:

You can look in PhoneGap for an example of sending messages to the delegate of the UIWebView. In a nutshell, you use document.location = "myscheme:mycommand?myarguments" then parse out the command and arguments from this delegate callback:

-(BOOL) webView:(UIWebView *)inWeb shouldStartLoadWithRequest:(NSURLRequest *)inRequest navigationType:(UIWebViewNavigationType)inType {
  if ( [[[inRequest URL] absoluteString] hasPrefix:@"myscheme:"] ) {
    //.. parse arguments
    return NO;
  }
}

You can see in the PhoneGap code that they set up a queue and timer to send the messages. Depending on your usage, you may need to do the same thing. There are other questions on SO on this topic.

Here is the Event Handling documentation. In my case I added event listeners to document from <body onload="myloader();">

function myloader() {
    document.addEventListener( 'touchcancel' , touch_cancel , false );
    document.addEventListener( 'touchstart' , touch_start , false );
    document.addEventListener( 'touchmove' , touch_move , false );
    document.addEventListener( 'touchend' , touch_end , false );
};

The actual event handling depends a lot on your needs. Each event handler will receive a TouchEvent with a touches property where each item is a Touch. You can record the start time and location in your touchstart handler. If the touches move to far or the wrong amount of time passes it is not a long touch.

WebKit may try to handle a long touch to start a selection and copy. In your event handler you can use event.preventDefault(); to stop the default behavior. I also found the -webkit-user-select:none css property handy for some things.

var touch = {};
function touch_start( event /*TouchEvent*/ {
  event.preventDefault();
  touch = {};
  touch.startX = event.touches.item(0).pageX;
  touch.startY = event.touches.item(0).pageY;
  touch.startT = ( new Date() ).getTime();
}

This is only the second project I have used javascript with. You can find better examples elsewhere.

As you can see this is no quick answer to your problem. I am pretty happy with the results I got. The html I was working with had no interactive elements beyond a link or two.

Thanks, I know nothing of Javascript; would you be so kind as to point me in the right direction on how to detect a tap in a UIWebView via Javascript and call an Objective-C method? I wouldn't mind being compatible with 3.0 for non-iPad targeting. For any others that only care about 3.2+, I fixed my issue by simply creating a transparent view right on top of the UIWebView and detecting the taps therein. — rscott, May 26 '10 at 03:24

score 45 · Answer 2 · answered Oct 22 '10 at 01:29

UIWebView has its own private views, which also has gesture recognizers attached. Hence, precedence rules keep any gesture recognizers added to a UIWebView from working properly.

One option is to implement the UIGestureRecognizerDelegate protocol and implement the method gestureRecognizer:shouldRecognizeSimultaneouslyWithGestureRecognizer. Return YES from this method for other tap gestures. This way you'll get your tap handler called, and the web view will still get its called.

See this on the Apple dev forums.

See the 2nd answer in question for supplemental information: http://stackoverflow.com/questions/2627934/simultaneous-gesture-recognizers-in-iphone-sdk — ChrisP, Apr 11 '11 at 21:35

score 13 · Answer 3 · answered Sep 16 '13 at 18:36

This is a somewhat hack-ish solution, but it works. UIWebView has a lot of internal gesture recognizers that you normally cannot access without using private API. You get them all for free, though, when you implement gestureRecognizer:shouldRecognizeSimultaneouslyWithGestureRecognizer:. At that point, you can tell all the internal UITapGestureRecognizers to only fire when your own UITapGestureRecognizer has failed. You only do that once and then remove the delegate from your own gesture recognizer. The result is that you can still pan and scroll your webView, but it won't receive any (single) tap gestures anymore.

- (void)viewDidLoad 
{      
    [super viewDidLoad];

    UITapGestureRecognizer *tap = [[UITapGestureRecognizer alloc] initWithTarget:self action:@selector(handleTapGesture:)];

    // view is your UIViewController's view that contains your UIWebView as a subview
    [self.view addGestureRecognizer:tap];

    tap.delegate = self;
}

- (void)handleTapGesture:(UITapGestureRecognizer *)gestureRecognizer
{
    NSLog(@"tap!");

    // this is called after gestureRecognizer:shouldRecognizeSimultaneouslyWithGestureRecognizer: so we can safely remove the delegate here
    if (gestureRecognizer.delegate) {
        NSLog(@"Removing delegate...");
        gestureRecognizer.delegate = nil;
    }
}

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldRecognizeSimultaneouslyWithGestureRecognizer:(UIGestureRecognizer *)otherGestureRecognizer
{
    if ([otherGestureRecognizer isKindOfClass:[UITapGestureRecognizer class]]) {
        [otherGestureRecognizer requireGestureRecognizerToFail:gestureRecognizer];

        NSLog(@"added failure requirement to: %@", otherGestureRecognizer);
    }

    return YES;
}

Enjoy!

score 5 · Answer 4 · edited Jan 12 '15 at 00:51

I was having the same problem. This solution worked for me:

1) Make sure to add the protocol to your interface: UIGestureRecognizerDelegate for example:

@interface ViewController : UIViewController <SlideViewProtocol, UIGestureRecognizerDelegate>

2) Add this line of code

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldRecognizeSimultaneouslyWithGestureRecognizer:(UIGestureRecognizer *)otherGestureRecognizer {
return YES
}

3) Setup gesture

UISwipeGestureRecognizer *swipeGesture = [[UISwipeGestureRecognizer alloc] initWithTarget:self action:@selector(nextSlide)];
swipeGesture.numberOfTouchesRequired = 1;
swipeGesture.direction = (UISwipeGestureRecognizerDirectionLeft);
swipeGesture.cancelsTouchesInView = YES; [swipeGesture setDelegate:self];
[self.view addGestureRecognizer:swipeGesture];

this answer should be edited to return the correct code in step # 2 (i.e. that API requires a BOOL to be returned). — Michael Dautermann, Nov 16 '13 at 11:12
This is the simplest of the solutions presented and works for me, with two caveats. You need to return YES. And you must set the swipeGesture.delegate = self; — JScarry, Feb 20 '14 at 20:21

score 3 · Answer 5 · answered Oct 26 '13 at 10:51

3

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldRecognizeSimultaneouslyWithGestureRecognizer:(UIGestureRecognizer*)otherGestureRecognizer {
    return YES;
}

answered Oct 26 '13 at 10:51

Bhoopi

6,523
3
22
16

score 2 · Answer 6 · answered Sep 06 '13 at 17:20

2

Another way is to put a transparent UIButton on top of UIWebView and handle taps from this button. In some cases it might be a good solution.

UIWebView webView = [UIWebView new];
//...

UIButton *transparentButton = [UIButton buttonWithType:UIButtonTypeCustom];
[transparentButton addTarget:self action:@selector(buttonTapped) forControlEvents:(UIControlEventTouchUpInside)];
transparentButton.frame = webView.frame;
transparentButton.layer.backgroundColor = [[UIColor clearColor] CGColor];
[self.view transparentButton];

answered Sep 06 '13 at 17:20

Sergey

47,222
25
87
129

Hahah, this is definitely the best solution :) +1 for the hack. – chrisallick Dec 12 '13 at 00:09
3

I use this method if I don’t need to scroll the UIWebView. But if you need to scroll, it doesn’t work since the UIButton traps all of the user input. – JScarry Feb 20 '14 at 19:41

score 1 · Answer 7 · edited May 23 '17 at 12:17

1

You may also find my answer here helpful. It's a working example of handling the pinch gesture in UIWebView's javascript.

(You could communicate the events back to the Objective-C if you wanted to. See my answer here.)

edited May 23 '17 at 12:17

Community

1
1

answered Sep 02 '10 at 21:37

zekel

9,227
10
65
96

Does UIGestureRecognizer work on a UIWebView?

7 Answers7

Linked