Title: Styling issue with Settings API
Last modified: April 4, 2017

---

# Styling issue with Settings API

 *  [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/styling-issue-with-settings-api/)
 * Hey. There is an interesting issue with the latest version (3.0). WooCommerce
   is adding a `‎` character before and after text inputs in settings. The one
   before the element is causing the box to be pushed over a few pixels. This makes
   it look funny when the text setting is above or below a non-text setting that
   doesn’t have this problem. I’ve been able to counteract the effect with a negative
   margin left of 3 pixels, but then it looks funny on Firefox because Firefox ignore
   the `‎` character.
 * The best example is in the Email tab page. You can see it in the “Header image”
   setting. If you inspect the element you will see the characters.
 * How can I solve this issue?
 * Thank you.

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

 *  Plugin Contributor [Claudio Sanches](https://wordpress.org/support/users/claudiosanches/)
 * (@claudiosanches)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/styling-issue-with-settings-api/#post-8992717)
 * Tested on Chrome and Firefox and I did not see anything different.
    Can you show
   a screenshot?
 *  Plugin Contributor [Claudiu Lodromanean](https://wordpress.org/support/users/claudiulodro/)
 * (@claudiulodro)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/styling-issue-with-settings-api/#post-8992758)
 * I can see it. In the Email Template settings page, the Header Image input is 
   a few pixels more right than the Footer Text input. We’ll have to address this
   in 3.0.1 by styling those with only CSS.
 * EDIT: [https://github.com/woocommerce/woocommerce/issues/13908](https://github.com/woocommerce/woocommerce/issues/13908)
    -  This reply was modified 9 years, 1 month ago by [Claudiu Lodromanean](https://wordpress.org/support/users/claudiulodro/).
 *  Thread Starter [bfl](https://wordpress.org/support/users/bfl/)
 * (@bfl)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/styling-issue-with-settings-api/#post-8992807)
 * Great! Thanks.
 * For [@claudiosanches](https://wordpress.org/support/users/claudiosanches/):
    ⌊
   Style Bug⌉
    -  This reply was modified 9 years, 1 month ago by [bfl](https://wordpress.org/support/users/bfl/).
    -  This reply was modified 9 years, 1 month ago by [bfl](https://wordpress.org/support/users/bfl/).
 *  Plugin Contributor [Claudio Sanches](https://wordpress.org/support/users/claudiosanches/)
 * (@claudiosanches)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/styling-issue-with-settings-api/#post-8992876)
 * Maybe I lose my design skills, but fixed: [https://github.com/woocommerce/woocommerce/pull/13909](https://github.com/woocommerce/woocommerce/pull/13909)
   
   Thanks for report it.

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

The topic ‘Styling issue with Settings API’ is closed to new replies.

 * ![](https://ps.w.org/woocommerce/assets/icon.svg?rev=3234504)
 * [WooCommerce](https://wordpress.org/plugins/woocommerce/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woocommerce/reviews/)

## Tags

 * [3.0](https://wordpress.org/support/topic-tag/3-0/)
 * [api](https://wordpress.org/support/topic-tag/api/)
 * [css](https://wordpress.org/support/topic-tag/css/)
 * [settings](https://wordpress.org/support/topic-tag/settings/)
 * [style](https://wordpress.org/support/topic-tag/style/)

 * 4 replies
 * 3 participants
 * Last reply from: [Claudio Sanches](https://wordpress.org/support/users/claudiosanches/)
 * Last activity: [9 years, 1 month ago](https://wordpress.org/support/topic/styling-issue-with-settings-api/#post-8992876)
 * Status: not resolved