The discussion revolves around the “Discourse Nav Item Icon / Emoji” theme component, which allows users to add icons or emojis before navigation items in Discourse. Don introduced the component, detailing its syntax for icons (icon:nav-item:icon-set:icon-name:icon-color) and emojis (emoji:nav-item:emoji-set:emoji-name:filter), with examples and screenshots demonstrating its use in desktop and mobile views Don. Davidkingham asked about compatibility with FontAwesome Pro, to which Don responded that it’s possible but requires modifying the component with SVGs and considering legal usage. Sheng_hualuo reported that the icon didn’t display on mobile after a Discourse update, and Lilly confirmed the issue in the dropdown navigation. Aaron_Walsh humorously noted the absence of a “follow-on” feature. Don acknowledged the issue, explaining that a recent Discourse update broke compatibility and that the desktop navigation version was removed in a fix to support the new mobile navigation Don. Sheng_hualuo expressed disappointment over the removal of the desktop version, highlighting its visual appeal.
filter: It makes the emoji color black in light mode and white in dark mode. If the emoji hovered or active it will be reveal with a transition. (optional)
For example: emoji:latest:twitter:rocket:filter emoji:top:google:star emoji:new:facebook_messenger:bell
Yeah, I think that’s possible but unfortunately I don’t have access to pro icon set. It works with icon svg so if you access to this than it should work. It requires to modify a little bit the component and add these SVGs. After that you can use it with the settings. And also important what is the legal usage of the pro icons svg on website what I am not sure.
Yeah, sorry this theme component and my others too which modified the navigation bar has to an update since this change DEV: replace list control nav dropdown with DMenuMobile (#28324) · discourse/discourse@931485b · GitHub. I will thinking of a solution. We can target easily the nav items in modal but the selected has no specific class unfortunately and I think we have to drop the desktop navigations from components.