Invalid CSS

Home › Forums › Product Support Forums › Ajax Search Pro for WordPress Support › Invalid CSS

This topic contains 2 replies, has 2 voices, and was last updated by ProjectMunton ProjectMunton 8 years, 10 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • January 14, 2015 at 11:10 pm #3460
    ProjectMunton
    ProjectMunton
    Participant

    Hi 🙂

    I love the plugin … but I have noticed that when using the web inspector there are hundreds of Invalid CSS property declarations … for e.g. there are 637 showing up on

    http://wp-dreams.com/demo/wp-ajax-search-pro3/

    I am starting to get a few questions about it. Is it something you are looking at?
    Many thanks in advance

    January 15, 2015 at 3:57 pm #3487
    Ernest Marcinko
    Ernest Marcinko
    Keymaster

    Hi!

    If you are referring to W3C CSS validations, than it’s probably right. Unfortunately the W3C validity does not allow many many properties like SVG fill, rgba backgrounds, background gradients and hundreds of other things. On the other hand every single major browser (including mobile) support these CSS features.
    If the search CSS complied the W3C CSS validity, then the plugin most likely would loose all the sales.

    If you check any wordpress theme, plugin or anything that has CSS files, you will probably find hundreds of errors with the W3C validator. As an example, check out the AVADA theme (300+ errors) or you can check out facebook as well (40 errors on the login page).

    There are many many lines of CSS in the plugin only for the proper compatibilty. Since this is a stock product, it has to work with millions of themes and plugins out there as well as with every major browser.

    Best,
    Ernest Marcinko
    If you like my products, don't forget to rate them on codecanyon :)


    January 17, 2015 at 8:57 pm #3535
    ProjectMunton
    ProjectMunton
    Participant

    Hi Ernest … appreciate the honest quick reply 🙂

    I understand the balance between compatibility and usability … the reason it has come up is it is the only plugin of dozens that we use which comes up with errors like this in Safari and Chrome Web Inspect … it just makes stakeholders a little nervous about Google indexing, penalties, backwards compatibility etc. It will just have to be factored in for any future projects / purchases

    Just one more item I have come across … I have added the latest version of the plugin to a local test setup (which ran the previous version) … We have a custom post type which is now not showing in the search results (it did previously) nothing has changed in the settings … and the custom post type is flagged to be searched in the settings.

    Is there anything I can check which could be causing the issue?

    Many thanks again

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.