Sans Emoji

A little help, when you need it.

Start with the checks below. Atlassian editors change over time, and different editors can handle autocomplete differently.

For other questions, contact the developer.

Quick checks

The emoji popup still appears

Check that Sans Emoji is enabled and has access to the page. Refresh your Atlassian tab after installation or an update. Supported pages use HTTPS on atlassian.net, atlassian.com or bitbucket.org, including subdomains. If it still appears, that editor may use markup the extension does not yet recognize.

Enter or Tab acts on an invisible suggestion

Press Escape to leave autocomplete. Some editors ignore the extension’s cancellation event even though the suggestion panel is hidden. If the problem continues, disable Sans Emoji and refresh the tab, then report the browser and editor you were using.

How do I insert an emoji?

Use the editor’s toolbar emoji picker. Sans Emoji suppresses colon-triggered searches, including intentional queries such as :smile. Existing emoji are left alone.

Does it work on our company’s own Jira domain?

Only if the page is on one of the supported domains above. Custom company domains, self-hosted installations elsewhere and frames with unrelated URLs are outside the extension’s scope.

Where are the settings?

There are no settings or toolbar popup. Sans Emoji works automatically on supported pages. To turn it off, disable it in your browser’s extension manager and refresh your Atlassian tabs.

Firefox removed my temporary installation

Temporary add-ons are removed when Firefox restarts. For local testing, load the built manifest again through about:debugging. Permanent installation in standard Firefox requires Mozilla signing. Sans Emoji requires Firefox 142 or later.

I rebuilt the extension, but nothing changed

Reload Sans Emoji in the browser’s extension manager, then refresh your Atlassian tabs. Both browsers now use the same dist folder. If you previously loaded a chrome or firefox subfolder, remove that old development installation and follow the current installation instructions.

When reporting a problem

A screenshot can help, but remove confidential issue text, private project names, personal details, passwords and session information. You do not need to share an internal issue URL.

For details about data handling, read the privacy policy.

Contact the developer

For questions, bug reports or privacy requests, email Sébastien Guillon at guillon.sebastien@gmail.com. For a bug report, include the details listed above.