Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support case where showPreview is false but showSkinTones is true. Also add prepare script. #277

Merged
merged 2 commits into from
Mar 8, 2019

Conversation

kayleema
Copy link

@kayleema kayleema commented Mar 8, 2019

It is useful to be able to disable the mouseover emoji preview area but still have showSkinTones available. In particular, in order to be able to use the component on iOS without having to double-click every time it is necessary to disable much mouseover behavior such as this. (see https://css-tricks.com/annoying-mobile-double-tap-link-issue/)

Also, it is useful to have a "prepare" script in the package.json so that it is possible to clone emoji-mart directly from a git repo without extra steps.

kayleema added 2 commits March 8, 2019 14:00
This is necessary in order to be able to show skin tone picker even when
one desires for the mouseover preview to be invisible. This is an
important case because mouseover displays must be disabled in order to
enable single click emoji typing on iOS without disabling the skin tone
picker.
@nolanlawson
Copy link

Could you provide some more details about what this PR is doing? I'm not sure I follow what exactly this fixes. Presumably mouseover is a desktop-only convention, but I suppose this change is mostly for mobile?

Also the "prepare" thing seems like a great fix but unrelated, would be good to have it in a separate PR since it seems very uncontroversial to me. :)

@nolanlawson
Copy link

Nevermind, after reading through the CSS Tricks article and this PR again, I understand. You're not trying to solve the iOS hover issue per se - that's just what led you to want to hide the mouseover preview but show the skin tones. However that doesn't work, so you opened this PR. Got it.

LGTM, merging!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants