Title: Styles CSS is wrongly HTML encoded
Last modified: April 26, 2024

---

# Styles CSS is wrongly HTML encoded

 *  Resolved [MaxD](https://wordpress.org/support/users/max-dayala/)
 * (@max-dayala)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/styles-css-is-wrongly-html-encoded/)
 * Hi,
 * I’m using Formidable Forms 6.9 with WordPress 6.5.2 and PHP 8.
 * One thing I’ve noticed is that I get some CSS errors in the file formidableforms.
   css with font-family names that need to be quoted.
 * I get this for example:
 *     ```wp-block-code
       .ss-content.frm_slimselect {
         font-size: 14px;
         font-family:"
         Lucida Grande"
         ,"
         Lucida Sans Unicode"
         ,Tahoma,sans-serif;
         height: auto;
         display: flex;
       }
       ```
   
 *     ```wp-block-code
       .ss-content.frm_slimselect {
       	font-size: <?php echo esc_html( $defaults['field_font_size'] ); ?>;
       	<?php if ( '' !== $defaults['font'] ) : ?>
       	font-family:<?php echo esc_html( $defaults['font'] ); ?>;
       	<?php endif; ?>
       	/* These rules fix conflicts with Boostrap 3 */
       	height: auto;
       	display: flex;
       }
       ```
   
 * When I look at the source code for pro_fields.css.php I can see that the esc_html()
   function is being used. This creates the character entities. Since the output
   is CSS, not HTML, this seems to me the wrong way to try and sanitize the output.
 * I can hack a solution myself to this, but it looks like it needs fixing.
 * Thanks
 * Max

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [Faisal Ahammad](https://wordpress.org/support/users/faisalahammad/)
 * (@faisalahammad)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/styles-css-is-wrongly-html-encoded/#post-17715624)
 * Hi Max,
 * The problem seems to be connected to their Pro plugin. Unfortunately, according
   to WordPress.org guidelines, they cannot provide support for the Pro plugin through
   these forums.
 * Please submit a ticket on their helpdesk website using the email address associated
   with your Pro license.
 * 👉🏽 [https://formidableforms.com/new-topic/](https://formidableforms.com/new-topic/)
 * Thank you
 *  Thread Starter [MaxD](https://wordpress.org/support/users/max-dayala/)
 * (@max-dayala)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/styles-css-is-wrongly-html-encoded/#post-17716227)
 * Thanks, I can do that.
 *  Plugin Support [Jonathan Martínez](https://wordpress.org/support/users/jonathanenlared/)
 * (@jonathanenlared)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/styles-css-is-wrongly-html-encoded/#post-17716353)
 * Hey [@max-dayala](https://wordpress.org/support/users/max-dayala/)
 * We appreciate you bringing this to our attention. Our dev team has logged this
   on our issue tracker.
 * Since this is a Pro issue. I encourage you to write us for any update regarding
   this issue using the link that [@faisalahammad](https://wordpress.org/support/users/faisalahammad/)
   shared:
   [https://formidableforms.com/new-topic/](https://formidableforms.com/new-topic/)

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Styles CSS is wrongly HTML encoded’ is closed to new replies.

 * ![](https://ps.w.org/formidable/assets/icon-256x256.png?rev=2588749)
 * [Formidable Forms - Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder](https://wordpress.org/plugins/formidable/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/formidable/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/formidable/)
 * [Active Topics](https://wordpress.org/support/plugin/formidable/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/formidable/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/formidable/reviews/)

 * 4 replies
 * 3 participants
 * Last reply from: [Jonathan Martínez](https://wordpress.org/support/users/jonathanenlared/)
 * Last activity: [2 years, 1 month ago](https://wordpress.org/support/topic/styles-css-is-wrongly-html-encoded/#post-17716353)
 * Status: resolved