A user oblio is experiencing issues with huge emojis when embedding Discourse posts on a Github Pages blog. gwwar suspects the problem is due to the class="emoji" attribute being scrubbed by an attribute whitelist during the import process.
After attempting to add img.emoji to the whitelist selector, oblio finds that the issue persists. gwwar believes this is a minor bug with the crawler aggressively scrubbing attributes from img tags.
The issue is identified as related to the Jekyll page using the Jemoji plugin, and the huge emojis coming from assets.github.com. gwwar submits a PR to address the issue.
Additionally, oblio suggests improving the whitelist field to clarify the separator and make editing more efficient. codinghorror agrees, and eviltrout adds placeholder values to the fields with examples of CSS values to address the concern.
(I’ve since deleted the topics but the bug is still present. The embedded emoji are shown 100%, as they are stored, while the forum ones seem to be shrinked)
The huge emoji’s are the ones coming from assets.github.com (the jemoji gem). This is probably a minor bug with the crawler too aggressively scrubbing attributes from img tags.
Edit: After looking at the config settings, could you show me what you have in:
I think that the best thing would be to change it to the token-type entry. See for example: “Required” → “exclude rel nofollow domains”.
If we’re at it, I propose another improvement for these kinds of field, they should tokenize on space and comma and other delimiters. This would make editing a lot more efficient. Right now you have to know that the separator is space and write everything and then Tab out, while the field separates the tokens. If it would just process the tokens during input, it would be a lot more user friendly, IMO. Write a word, space, token appears or write a word, comma, token appears.
Should I add this as a separate suggestion? (if you think it’s worth it)
