Add new <Emoji/> component or prop that doesn't use <Button/>?
See original GitHub issueI use the <Emoji/>
component in multiple places where it doesn’t need to be clickable, seems odd to render it as a <Button/>
in those cases.
Might be nice to either add a new component that renders it visually as before, or add a prop to switch between button and non button?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Adding emojis to your React app - LogRocket Blog
There are multiple ways to add emojis into your React app. Here's a short guide to fit almost every single use case.
Read more >Using Emojis in HTML, CSS, and JavaScript - KIRUPA
You have two ways of being able to do this, each with a varying degree of funness. One way is by using the...
Read more >How to add Emoji's in your website, using HTML, CSS or ...
In CSS you need to use the ::before or ::after pseudo-element coupled with the content property where you paste the Emoji as the...
Read more >Add emojis to input - javascript - Stack Overflow
Include the Emoji Picker in the component that holds the input's state and call it's setter (assuming you use functional components, call this....
Read more >How to Create a Custom Component with Emoji in ... - YouTube
In this video you will learn: 1. How you can create custom component with input and output property 2. How you can use...
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
Decided to go this way:
<button>
withtype=button
(thanks for the tip) only when emoji is clickable (not by default)<span>
otherwiseHandled in #329
Perhaps it would be simpler to just use a prop after all.
clickable={false}
or something like that.