Closed kuzzmi closed 7 years ago
This was also mentioned in the #205
This feels like a hack. Do we know why click events aren't propagating properly? is it because we're incorrectly stopping cancelling / stopping propagation elsewhere in the stack?
It is, and it's not at the same time. It's hard to tell why onClick
doesn't work, as tests are broken, however this is the only way to make it working right now. The only reason why IMO it might make sense to have this workaround is that currently clicking doesn't work at all and people fork this repo exactly for applying this "fix".
I'd be happy to fix the root cause, however I couldn't identify it, and it will take a while to fix the tests, so we can isolate this root cause.
Cool, I'll merge this, but can you open a followup Issue to "Remove the onMouseDown hack from #235" ?
Added #237 issue to get rid of this hack.
onClick
is not fired when clicked on a TypeaheadOption. This adds aonMouseDown
workaround with the same handler to handle clicks by default.Adds tests to test
onClick
andonMouseDown
events,onClick
test is set as pending until resolved.Since the whole master branch test suit fails as mentioned in #229, these tests couldn't be verified, but should be fine as soon as the main issue is resolved.