Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Nested child element not showing for concurrent events
See original GitHub issueval tp=new EventBus[Unit]()
div(button("click",(onClick() mapTo(()))-->tp ),
child<--(tp.$ mapTo div("clicked1", child <-- (tp.$ mapTo (div("clicked2")))))
)
clicked1 is shown but not clicked2,I guess maybe div(“clicked2”) needs some delay?
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
React JS Nested elements both use same onClick event and ...
To fix this I used the suggested e.stopPropagation(); and added an onChange event to the child element. However, now only the parent div...
Read more >Avoid Nesting when you're Testing - Kent C. Dodds
I want to show you something. What I'm going to show is a general testing principle, applied to a React component test.
Read more >Attached and Detached Child Tasks | Microsoft Learn
An attached child task is a nested task that is created with the TaskCreationOptions.AttachedToParent option whose parent does not ...
Read more >Enabling Routing in Nested Components - SAPUI5 SDK
When the nested component myreuse has routing enabled, the router instance within the myreuse component fires on its own a titleChanged event once...
Read more >3 Ways to Communicate Between Components in Blazor
In this post, I show you 3 different options you can use to manage communication between components in your Blazor applications.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks! Happy Chinese New Year!
Just added a test verifying that the next version of Laminar (developed in #8) fixes the original issue filed here despite this not being the intended usage.