Title: CSS errors
Last modified: August 30, 2016

---

# CSS errors

 *  [lauratraveler](https://wordpress.org/support/users/lauratraveler/)
 * (@lauratraveler)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/css-errors-8/)
 * Hi!
 * I get the following CSS errors:
 * `Feature -webkit-min-device-pixel-ratio doesn't exist for media null ), (min-
   resolution: 192dpi){body #kad-banner #logo .kad-standard-logo, .trans-header .
   is-sticky #kad-banner #logo .kad-standard-logo{background-image:url("http://www.
   travelersuniverse.com/wp-content/uploads/2015/03/logo.png") !important}}`
 * `Feature -webkit-min-device-pixel-ratio doesn't exist for media null ), (min-
   resolution: 192dpi){.trans-header #kad-banner #logo .kad-standard-logo-tranbg{
   background-image:url("http://www.travelersuniverse.com/wp-content/uploads/2015/
   03/logo.png") !important}}`
 * `.product_item .product_details h5, .product-category.grid_item a h5 - Value 
   Error : font-style 700 is not a font-style value : 700`
 * How can I correct them?
 * Thanks!

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

 *  [hannah](https://wordpress.org/support/users/hannahritner/)
 * (@hannahritner)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/css-errors-8/#post-6416628)
 * Where are you seeing these? Have you tried deactivating your plugins to test?
 * Hannah
 *  Thread Starter [lauratraveler](https://wordpress.org/support/users/lauratraveler/)
 * (@lauratraveler)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/css-errors-8/#post-6416633)
 * You can see one of my pages tested here jigsaw.w3.org/css-validator/validator?
   uri=http%3A%2F%2Fwww.travelersuniverse.com%2Fthings-to-do-brussels&profile=css3&
   usermedium=all&warning=1&vextwarning=&lang=en
 * It actually has many more errors in the themes/pinnacle/assets/css/pinnacle.css?
   ver=128
 * And this other error as well
 * `Parse Error }// Post Class .product_list_widget li, .kadence_social_widget a,.
   widget_categories li a,.widget_archive li a, .widget_recent_entries li a, .widget_nav_menu
   li a, .widget_pages li a, .product-categories li a, .product-categories li a{
   background:#fff}`
 * I’ve already corrected about 80 errors, but I have no idea what to do with these
   ones.
 * Thanks!
 *  [Ben Ritner – Kadence WP](https://wordpress.org/support/users/britner/)
 * (@britner)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/css-errors-8/#post-6416634)
 * Hey,
    Oh the “validator”… it’s not errors at least not the kind you want to “
   fix” that css is written for maximum browser support and the “validator” is only
   looking at valid css but let me tell you there is tons of browser specific css
   and you want it.
 * Prime example is: @-moz-keyframes
 * I don’t see any errors that would actually effect your site in any way.
 * Kadence Themes
 *  Thread Starter [lauratraveler](https://wordpress.org/support/users/lauratraveler/)
 * (@lauratraveler)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/css-errors-8/#post-6416657)
 * Well, I know Google doesn’t love errors, so I believe the aim is a site without
   errors.
 * Even more so if the error is related with something I don’t use. Like, for example,
   the cart. I’ll probably never have a cart on my site, so having this woocommerce
   error, is not adding any extra functionality. While the user can’t see any difference,
   the search engines can see an error.
 * `.woocommerce ul.digital-downloads li, .woocommerce-page ul.digital-downloads
   li Parse Error ;.woocommerce ul.digital-downloads li .count,.woocommerce-page
   ul.digital-downloads li .count{float:right}`
 *  [Ben Ritner – Kadence WP](https://wordpress.org/support/users/britner/)
 * (@britner)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/css-errors-8/#post-6416688)
 * Hey,
    To be clear. Search engines don’t see a validator error. It’s not a true
   error. Now if your site has consle errors thats different. Let me try to help
   prove the point a little more… look here: [http://jigsaw.w3.org/css-validator/validator?uri=google.com&profile=css3&usermedium=all&warning=1&vextwarning=&lang=en](http://jigsaw.w3.org/css-validator/validator?uri=google.com&profile=css3&usermedium=all&warning=1&vextwarning=&lang=en)
 * Thats google.com. And it has 10 “errors”, 14 “warnings”.
 * Validator is a tool to use with understanding it’s not what is used in terms 
   of a site score or anything like that.
 * Hope that clarifies?
 * Kadence Themes

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

The topic ‘CSS errors’ is closed to new replies.

 * ![](https://i0.wp.com/themes.svn.wordpress.org/pinnacle/1.8.10/screenshot.png)
 * Pinnacle
 * [Support Threads](https://wordpress.org/support/theme/pinnacle/)
 * [Active Topics](https://wordpress.org/support/theme/pinnacle/active/)
 * [Unresolved Topics](https://wordpress.org/support/theme/pinnacle/unresolved/)
 * [Reviews](https://wordpress.org/support/theme/pinnacle/reviews/)

 * 5 replies
 * 3 participants
 * Last reply from: [Ben Ritner – Kadence WP](https://wordpress.org/support/users/britner/)
 * Last activity: [10 years, 10 months ago](https://wordpress.org/support/topic/css-errors-8/#post-6416688)
 * Status: not resolved