# Why katalon can't recognize 'tap' issue in webview mode?

**URL:** <https://forum.katalon.com/t/why-katalon-cant-recognize-tap-issue-in-webview-mode/11327>\
**Category:** Mobile Testing\
**Tags:** mobile-testing, katalon-studio\
**Created:** [June 4, 2018, 1:35am UTC](https://forum.katalon.com/t/why-katalon-cant-recognize-tap-issue-in-webview-mode/11327 "2018-06-04T01:35:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wen](https://avatars.discourse-cdn.com/v4/letter/w/f9ae1b/32.png) [@wen](https://forum.katalon.com/u/wen)\
**Post date:** [June 4, 2018, 1:35am UTC](https://forum.katalon.com/t/why-katalon-cant-recognize-tap-issue-in-webview-mode/11327/1 "2018-06-04T01:35:53Z")

</div>

My developer use ‘tap’ in his code not click, because he said ‘tap’ is faster than click, when I test his code I switch to webview I can’t use katalon to trigger the click issue on the element as so as using ‘tap’, But when I use chrome inspector I can use $(“XXX”).trigger(‘tap’) to trigger the issue. it confuse me. I think that if my developer don’t change his code. The case can’t be repaired?  
If there is any one have the solution please reply on it, thank you!

---

<div class="post-metadata">

**Author:** ![albert.vu](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/albert.vu/32/20595_2.png) [@albert.vu](https://forum.katalon.com/u/albert.vu)\
**Post date:** [August 8, 2022, 7:11am UTC](https://forum.katalon.com/t/why-katalon-cant-recognize-tap-issue-in-webview-mode/11327/2 "2022-08-08T07:11:36Z")

</div>