# Handle Events in Controls under NativeViewHost

**URL:** <https://forums.fusetools.com/t/handle-events-in-controls-under-nativeviewhost/1360>\
**Category:** How-to Discussions\
**Created:** [April 30, 2017, 10:15am UTC](https://forums.fusetools.com/t/handle-events-in-controls-under-nativeviewhost/1360 "2017-04-30T10:15:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bishaka\_Samuel](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/bishaka_samuel/32/234_2.png) [@Bishaka\_Samuel](https://forums.fusetools.com/u/Bishaka_Samuel)\
**Post date:** [April 30, 2017, 10:15am UTC](https://forums.fusetools.com/t/handle-events-in-controls-under-nativeviewhost/1360/1 "2017-04-30T10:15:54Z")

</div>

Here’s my code, for some reason boo is not being called.

I suspect the mapview is taking over the tapped event because when you tap the text, the map zooms in.

Anyway i can prevent this bubbling of events like in the HTML DOM spec?

```auto
<Page ux:Class="MapPage">	
	<ux:Include File="../shared/fonts.ux"/>
	<JavaScript>	
		var boo = function(){
			console.log("Text clicked on map view!");
		}
		module.exports = {
			boo:boo
		}
	</JavaScript>
	<Panel>		
		<NativeViewHost>
			<DockPanel>
				<Panel Dock="Top" Height="60" Color="#ffffff" Margin="0,40,0,0" Padding="20,20,20,20" Width="90%">					
					<Text Font="Light" Clicked="{boo}">Request package delivery</Text>
				</Panel>			
			</DockPanel>
		    <MapView Latitude="59.911567" Longitude="10.741030" Zoom="10" ShowMyLocation="True">
		        <MapMarker Latitude="59.911567" Longitude="10.741030" Label="Fuse HQ"/>
		    </MapView>
		</NativeViewHost>		
	</Panel>
</Page>

```

---

<div class="post-metadata">

**Author:** ![Uldis](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/uldis/32/657_2.png) [@Uldis](https://forums.fusetools.com/u/Uldis)\
**Post date:** [April 30, 2017, 10:41am UTC](https://forums.fusetools.com/t/handle-events-in-controls-under-nativeviewhost/1360/2 "2017-04-30T10:41:36Z")

</div>

This is a known issue that we have an internal ticket on. You can expect it to be fixed in a future release.