Clickable option on the demo doesn't work

[chulanovskyi]

At the very bottom of the demo site there is a section with a clickable prop example, but - the problem is described in the title. When I try to type something into the input - it doesn't react on any event, clicking, typing...

OS: 18.04.2 LTS
Tested browsers:

• Chrome Version 75.0.3770.100 (Official Build) (64-bit)
• Firefox 67.0.4 (64-bit)

[aronhelser]

This should be a matter of setting the `pointer-events` style correctly - I thought this worked when the example was added. Can you take a look?

…

On Tue, Jun 25, 2019 at 9:20 AM Oleg Chulanovskyi ***@***.***> wrote: At the very bottom of the demo site <https://react-tooltip.netlify.com/> there is a section with a clickable prop example, but - the problem is described in the title. When I try to type something into the input - it doesn't react on any event, clicking, typing... [image: image] <https://user-images.githubusercontent.com/13966263/60101580-aeff4700-9764-11e9-898d-e18542a14c48.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#499>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEX6THNGXWZ4ZYDB3HBW6R3P4ILQZANCNFSM4H3IHQCQ> .

[chulanovskyi]

Tested on mobile (chrome) - still not working. Will check later from the desktop...

Update:
@aronhelser tested on desktop (Windows, Chrome) - nope, doesn't work...

[tihuan]

It looks like the example site's index.js response doesn't have .__react_component_tooltip.allow_click css rule. Possibly because standalone/react-tooltip.js doesn't have that rule?

E.g.,

https://github.com/wwayne/react-tooltip/blob/master/standalone/react-tooltip.js

For allow_hover, there's __react_component_tooltip.allow_hover{pointer-events:auto}, so I for allow_click, was expecting to see __react_component_tooltip.allow_click{pointer-events:auto} there as well?

Could this be the root cause?

Thanks!

@aronhelser

Context Issue: #417 (comment)

[mawburn]

Any updates on this? It seems like it extends into the library itself and setting the clickable option doesn't do anything.

[roggervalf]

Hi @chulanovskyi, already fixed in the new release, let me know if it works for you.