# haxe-ui
- b
billowy-waiter-28954
03/01/2023, 6:09 PMI don't think Ceramic is doing anything weird here - b
bright-gpu-74537
03/01/2023, 6:09 PMnor haxeui - b
bright-gpu-74537
03/01/2023, 6:10 PM... ... ... slowly looks at NotBilly... 😄 - b
bright-gpu-74537
03/01/2023, 6:12 PM - b
bright-gpu-74537
03/01/2023, 6:12 PMis this what it looks like still? Is this "right"? - a
ambitious-knife-25690
03/01/2023, 6:12 PMcorrect - a
ambitious-knife-25690
03/01/2023, 6:13 PMonly one event is triggered not 2 - a
ambitious-knife-25690
03/01/2023, 6:13 PMMy testcase demo'd this 🤔 - b
bright-gpu-74537
03/01/2023, 6:14 PMok, so i think there is crossed wires, or misexplanation on my part... in cermaic you just metioned that it will only get one event, ie, the child will swallow the event for the parent - b
billowy-waiter-28954
03/01/2023, 6:15 PMyes that's it - b
bright-gpu-74537
03/01/2023, 6:16 PMok, i dont think that is "standard" behaviour, not that there is a standard, but browsers or my exp with other frameworks... anyways, looks like NB has a workaround 🙂 - a
ambitious-knife-25690
03/01/2023, 6:17 PMI don't think I do - a
ambitious-knife-25690
03/01/2023, 6:17 PMalso can we talk in one channel 😆 - a
ambitious-knife-25690
03/01/2023, 6:20 PMhmm, this seems confusing - a
ambitious-knife-25690
03/01/2023, 6:20 PMI wonder if intercepting would be enough... i guess i'll test that in the mean time - a
ambitious-knife-25690
03/01/2023, 6:21 PMeven if it does, it only seems to be down and over, which isn't the full event list that haxeui may require - b
bright-gpu-74537
03/01/2023, 6:21 PMi would try Jeremy's suggestion and see if it improves things, but i can think of many times in haxeui, and user code, where there very well may be events in parents and children (mouse events or otherwise) - a
ambitious-knife-25690
03/01/2023, 6:23 PMon it 😄 - b
billowy-waiter-28954
03/01/2023, 6:40 PM😅 - a
ambitious-knife-25690
03/01/2023, 8:22 PMalmost - a
ambitious-knife-25690
03/01/2023, 8:22 PMi can't click on items - a
ambitious-knife-25690
03/01/2023, 8:25 PMtestcase seems to work - a
ambitious-knife-25690
03/01/2023, 8:36 PMi'm getting mouse down/up events from the dropdown - a
ambitious-knife-25690
03/01/2023, 8:36 PMeverything appears to be working except for click mousedown/up 🤔 - a
ambitious-knife-25690
03/01/2023, 8:46 PMvirtual listview works 100% but the normal ones don't let me select the row - a
ambitious-knife-25690
03/01/2023, 11:29 PMhmmm, tree view and normal list views both don't fully work - a
ambitious-knife-25690
03/01/2023, 11:29 PMwhat is different about these guys 🤔 - a
ambitious-knife-25690
03/01/2023, 11:53 PMreally not sure, clicking triggers the mousedown event on a dropdown - a
ambitious-knife-25690
03/02/2023, 12:52 AM!!!!! - a
ambitious-knife-25690
03/02/2023, 12:57 AMI think I have figured out what is going on with my clipping implementation. If a child of a parent specifies a clipping rectangle, the parent clipping rect no longer works. In the above example I add a clip rect and it works fine, but as soon as I add a clip rect to a child of the larger square the clip rect no longer works. This seems similar to the event handling issue where a child takes priority. Is this intentional? If so, how does one achieve nested clipping in ceramic? @billowy-waiter-28954