This is due to the scrollbar taking up too much space. On browsers with no "physical" scrollbar there is no issue

This is probably due to the default configuration of the library.

It fetches images at cdnjs.cloudflare.com whereas the base emoji plugin fetches them at cdn.jsdelivr.net.

It also load additional css and js files from cdnjs.cloudflare.com. These files are probably already included in the core and should not be fetched again.

Add a option to translate categories:

• Recent
• Smileys & People
• Animals & Nature
• Food & Drink
• Activity
• Travel & Places
• Objects
• Symbols
• Flags

From https://discuss.flarum.org/d/4787-emoji-picker/42

The EmojiOne Area plugin uses a data: image in the CSS for the default button.

In my extension this default icon is hidden and another is used with the core icon() helper.

But the image is still in the CSS and still triggers CSP error if data: is not allowed by the img-src rule. It does not prevent the use of the plugin, but it will spam the CSP report URI if enabled.

It might be a good idea to extract the useful parts of the CSS into extension.less and not import all the original rules.

Hello, could you update the emoji to the latest version which is available? Or give tips on how to do it?

Not flarum style button emoji picker

I received a report that in Firefox if a text with Emoji in the middle is select than is used "quote" the text after the smiles are not quoted.

I tested this in Firefox stable and developers and the issue is present.
Is not present in Chrome based browser.

I was thinking to report this bug to the WebCompat but there is no demo about this that they can test for reproduce the issue.

Also I tried to reproduce the issue with "normal Emoji means with no extension" and I was unable to reproduce the issue on Firefox. So the issue is the Firefox browser or the extension? How can we report the bug if is a browser bug?

https://www.screencast.com/t/usihW1Pyr0kZ
https://www.screencast.com/t/eEQUbZvL

Things that have been asked and are not (yet) available in the emojionearea plugin.
I'll take these ideas into account if I create my own popup in the future.

• Ability to search emojis
• Be aware of left/right borders and not go out of screen (linked with next one)
• Change number of emojis per row request, request

Good work! Thought you'd appriciate some feedback. Here's what I found:

Should probably extract to separate class: https://github.com/clarkwinkelmann/flarum-ext-emojionearea/blob/master/bootstrap.php#L12

Maybe this should be a div? https://github.com/clarkwinkelmann/flarum-ext-emojionearea/blob/master/js/forum/src/components/EmojiAreaButton.js#L19

Use const: https://github.com/clarkwinkelmann/flarum-ext-emojionearea/blob/master/js/forum/src/components/EmojiAreaButton.js#L26

Use const and send texteditor as parameter: https://github.com/clarkwinkelmann/flarum-ext-emojionearea/blob/master/js/forum/src/main.js#L13

What is the status of translations provided in https://github.com/clarkwinkelmann/flarum-ext-emojionearea/tree/master/locale? I'm trying to cleanup redundant translations from Weblate - if translation for given language is already bundled with extension, there is no sense to have it duplicated in Weblate. But this is true only for actively maintained translations, which usually means only translations maintained by extension author. For example if extension author knows Italian, he can provide en and it translations, while the rest should probably be handled inside of respective language packs. So now I'm trying to figure out which translations are available because of extension author knows this language and will be able to maintain them, and which are just leftovers from old days where translations were contributed by community to extensions instead of language packs (in that case translations may become outdated after some times, since nobody will update them).

So how does it looks like for https://github.com/clarkwinkelmann/flarum-ext-emojionearea/tree/master/locale? Which languages do you know and will be able to update if any change will be needed?

I want to be able to manage categories separately, modify category icons, and temporarily turn off the use of certain expressions. Because in some areas, some expressions may face regulatory and copyright issues

Will this extension be compatible with beta8?