Custom HTML/CSS | Community
Skip to main content

Custom HTML/CSS

  • May 21, 2025
  • 4 replies
  • 0 views
Jesse12

We add custom HTML/CSS to some articles as a way to draw the attention of our customers. When I used the new editor, whether it's on a new article or migrating an existing article to the new editor, the custom HTML/CSS appears to merge itself into the next class. 

 

Using the legacy editor and works as expected:

 

Using the new editor and does not work as expected:

 

This causes the text not to appear as we want it to when previewing or publishing the article.

Due to this, we have to switch back to the legacy editor, update our changes again to ensure that it appears properly and then publish the article.

 

    4 replies

    Patrycja12

    @jesse12 

    Thank you for reporting this issue and providing such a clear explanation and examples.  Our engineering team will be investigating this further to understand what’s causing the issue and how we can address it.

    In the meantime, as a temporary workaround, you can use a <div> element for the outer container instead of a <span>. By adding your CSS class to the <div> and setting its display property to inline (e.g., style="display: inline"), it should behave in a similar way to your previous setup and display as expected.
     

    Please let us know if this workaround is helpful or if you run into any other difficulties. 

     

     

    Jesse12
    • Jesse12
    • Author
    • May 23, 2025

    Thanks @patrycja12 

    The recommendation has worked.


     

      Patrycja12

      @jesse12 This issue has been fixed and any workarounds should no longer be necessary

      Jesse12
      • Jesse12
      • Author
      • May 28, 2025

      Thanks @patrycja12 

       

      I confirm that it's working as expected in the new editor.

        Terms & ConditionsCookie settingsAccessibility statement