Discourse has changed how tag separators are implemented, moving from CSS pseudo-elements to proper HTML for better accessibility and functionality. This change allows for easier customization of tag separators using JavaScript value transformers. For example, to remove commas entirely or replace them with pipes. awesomerobot explains the process and provides code examples. Some users reported issues with duplicate commas, which Arkshine attributed to the Multilingual plugin using the old CSS method. jesus2099 and Olle11 discussed the plugin’s impact on language settings and tag separators. nolo noted that separators are hidden by default for box or bullet tag styles but may still appear on mobile due to specific CSS declarations.
Previously we used a CSS pseudo element to add the commas, which isn’t ideal because the content isn’t technically available as part of the document — screenreaders can’t access it, they’re not selectable, web crawlers can’t see them…
For most sites this won’t change anything obvious, but if you previously removed or changed the tag separator you’ll have to use a value transformer instead of CSS.
This is a fairly straightforward process with JS, for example if you want to remove the comma entirely:
I wanted to try and installed the Multilingual plugin and when I tried it the double commas came up. When I try to deactivate the plugin my language becomes English (and hence the double commas dissapear). When I activate it again it becomes my language again.
Do you think I should remove the plugin if I don’t really need it for now, and if so why is the language now in English? The ‘default locale’ is blank when deactivating the multilingual plugin.
If the plugin does not effect the website in any way maybe I can keep it and try to remove the double commas.