Title: inline style error
Last modified: January 25, 2019

---

# inline style error

 *  Resolved [edit4ever](https://wordpress.org/support/users/edit4ever/)
 * (@edit4ever)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/inline-style-error/)
 * Currently printfriendly is changing inline style code which causes issues with
   printing some elements.
 * It changes this:
    `<span style="width: 80%"></span>`
 * Into this:
    `<span orig-style="width: 80%"></span>`
 * By changing style= to orig-style= the items do not get styled properly for printing.
 * Please fix or add option to leave inline style code in place.
 * Thank you!
    -  This topic was modified 7 years, 3 months ago by [edit4ever](https://wordpress.org/support/users/edit4ever/).
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Finline-style-error%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Author [Print & PDF by PrintFriendly](https://wordpress.org/support/users/printfriendly/)
 * (@printfriendly)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/inline-style-error/#post-11143606)
 * Currently we don’t support inline styles. We’re looking into ways to support.
   To solve now, use the custom CSS feature.
 * Use CSS specificity or add a class to the span.
 * **Add a class to the element.**
 * `<span style="width: 80%" class="myWidth"></span>`
 * **Use this in your custom CSS**
 *     ```
       #printfriendly .myWidth{
         width:80%;
       }
       ```
   
 *  Thread Starter [edit4ever](https://wordpress.org/support/users/edit4ever/)
 * (@edit4ever)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/inline-style-error/#post-11144063)
 * Thank you for looking into ways to support this!
 * Unfortunately the span width I am referring to is generated by quiz results and
   is different for every span and every user based on test answers. That is why
   it can’t be a hard code in the custom css. It has to remain as inline styling.
 * Hopefully you are able to find a solution.
 *  Plugin Author [Print & PDF by PrintFriendly](https://wordpress.org/support/users/printfriendly/)
 * (@printfriendly)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/inline-style-error/#post-11200329)
 * [@edit4ever](https://wordpress.org/support/users/edit4ever/) We’re going to fix
   this. We will stop removing inline styles for WordPress. Give us 7-10 days to
   get it live. You will not need to update the plugin, the change happens on our
   side.
 * If you have a minute, please give us a review on WordPress. [https://wordpress.org/plugins/printfriendly/](https://wordpress.org/plugins/printfriendly/)
 *  Thread Starter [edit4ever](https://wordpress.org/support/users/edit4ever/)
 * (@edit4ever)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/inline-style-error/#post-11202763)
 * Thanks for this! Hope it helps others as well. I’ll be sure to review…and thanks
   for the quick responses.
 * P.S. another suggestion is to add the custom css into the settings section so
   we don’t have to edit a file on the server.

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

The topic ‘inline style error’ is closed to new replies.

 * ![](https://ps.w.org/printfriendly/assets/icon-256x256.png?rev=2951152)
 * [Print, PDF, Email by PrintFriendly](https://wordpress.org/plugins/printfriendly/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/printfriendly/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/printfriendly/)
 * [Active Topics](https://wordpress.org/support/plugin/printfriendly/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/printfriendly/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/printfriendly/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [edit4ever](https://wordpress.org/support/users/edit4ever/)
 * Last activity: [7 years, 3 months ago](https://wordpress.org/support/topic/inline-style-error/#post-11202763)
 * Status: resolved