# haxe-ui
- b
bright-gpu-74537
03/01/2023, 4:56 PMas not billy said the simplest way would be to restyle the checkbox, working example: http://haxeui.org/builder/?6a69d6c7 - a
ambitious-knife-25690
03/01/2023, 5:02 PM@bright-gpu-74537 How does haxeui manage the events from a backend perspective? - a
ambitious-knife-25690
03/01/2023, 5:02 PMIt seems like the way ceramic works is if a child listens to a pointer event, it will steal focus from the parent - a
ambitious-knife-25690
03/01/2023, 5:03 PMso for something like a dropdown that is likely composed of multiple parts - do all the children listen to pointer events in some way? - b
bright-gpu-74537
03/01/2023, 5:03 PMwhat do you mean "steal focus"? - b
bright-gpu-74537
03/01/2023, 5:04 PMyeah, each item renderer will be listening for mouse events - a
ambitious-knife-25690
03/01/2023, 5:04 PMhttps://media.discordapp.net/attachments/853414608747364352/1080523580061790268/gif.gif▾
- a
ambitious-knife-25690
03/01/2023, 5:04 PMso this is essentially what is happening in the backend - a
ambitious-knife-25690
03/01/2023, 5:05 PMwhere the upper pink square is a child of the larger green square - a
ambitious-knife-25690
03/01/2023, 5:05 PMbut because it sets a pointer event, it steals focus - a
ambitious-knife-25690
03/01/2023, 5:05 PMwhich is where my interaction issues with particular components in the backend is coming from it seems like - b
bright-gpu-74537
03/01/2023, 5:06 PMso you are saying if you have a box in a box, and both have mouse handlers, then only the sub box will get the event? - a
ambitious-knife-25690
03/01/2023, 5:06 PMyeah - a
ambitious-knife-25690
03/01/2023, 5:08 PMremoving the pointer events from the pink square and things work as one would expect - b
bright-gpu-74537
03/01/2023, 5:08 PMseems like odd beahviour for ceramic... not sure the easiest way to work around it - a
ambitious-knife-25690
03/01/2023, 5:08 PMi'm a bit confused here as well - a
ambitious-knife-25690
03/01/2023, 5:09 PMcause there are going to be components with multiple reasons to click within a single parent - b
bright-gpu-74537
03/01/2023, 5:09 PMthere are various cases where you might have a component tree with click events all over the place - a
ambitious-knife-25690
03/01/2023, 5:12 PMit is intended to work like this - a
ambitious-knife-25690
03/01/2023, 5:13 PMI can understand it, but from a haxeui side I'm not sure how to circumvent it - a
ambitious-knife-25690
03/01/2023, 5:14 PMor even work with it somehow - a
ambitious-knife-25690
03/01/2023, 5:15 PMwith the drop down example, why does the select box have multiple event listeners? - a
ambitious-knife-25690
03/01/2023, 5:16 PM(the box you click on to open the drop down) - a
ambitious-knife-25690
03/01/2023, 5:16 PMshouldn't that just be a single event? - b
bright-gpu-74537
03/01/2023, 5:18 PMdoes it have multiple? - a
ambitious-knife-25690
03/01/2023, 5:19 PMit must due to the children stealing focus - a
ambitious-knife-25690
03/01/2023, 5:19 PMI'm not sure how to confirm it tho - b
bright-gpu-74537
03/01/2023, 5:20 PM> it must due to the children stealing focus i think thats an assumption... afaik, it should just have up / down handlers - b
bright-gpu-74537
03/01/2023, 5:21 PMput a trace in your mapEvent, spit out the component ids and event types of things that are asking to be mapped - a
ambitious-knife-25690
03/01/2023, 5:21 PMokay will do 👍