[Plugin: Social Media Widget] W3C CSS Validator: 28 Errors

  • naturalgirl

    (@naturalgirl)


    13 years, 3 months ago

    Someone told me I need to fix the errors on my site and most are from this plugin when I put it in to a CSS Validator. I don’t see an answer for this in any questions. Please help.

    My site is http://www.4usnaturals.com

    _______________________________________________________________________

    4 .socialmedia-buttons Value Error : margin-top Too many values or values are not recognized : 5px 0 0 0 5px 0 0 0
    40 .socialmedia-buttons img.fade:hover Property opacity doesn’t exist in CSS level 2.1 but exists in : 1 1
    41 .socialmedia-buttons img.fade:hover Property -moz-opacity doesn’t exist : 1 1
    42 .socialmedia-buttons img.fade:hover Property -webkit-transition doesn’t exist : all 0.2s ease-in all 0.2s ease-in
    43 .socialmedia-buttons img.fade:hover Property -moz-transition doesn’t exist : all 0.2s ease-in all 0.2s ease-in
    44 .socialmedia-buttons img.fade:hover Property transition doesn’t exist : all 0.2s ease all 0.2s ease
    48 .socialmedia-buttons img.scale:hover Property -moz-transform doesn’t exist : scale(1.2) scale(1.2)
    49 .socialmedia-buttons img.scale:hover Property -webkit-transform doesn’t exist : scale(1.2) scale(1.2)
    50 .socialmedia-buttons img.scale:hover Property -webkit-transition doesn’t exist : all 0.2s ease-in all 0.2s ease-in
    51 .socialmedia-buttons img.scale:hover Property -moz-transition doesn’t exist : all 0.2s ease-in all 0.2s ease-in
    52 .socialmedia-buttons img.scale:hover Property -ms-zoom doesn’t exist : 1.2 1.2
    53 .socialmedia-buttons img.scale:hover Property transition doesn’t exist : all 0.2s ease all 0.2s ease
    57 .socialmedia-buttons img.bounce:hover Property transform doesn’t exist : translate(0,-2px) translate(0,-2px)
    58 .socialmedia-buttons img.bounce:hover Property -moz-transform doesn’t exist : translate(0,-2px) translate(0,-2px)
    59 .socialmedia-buttons img.bounce:hover Property -webkit-transform doesn’t exist : translate(0,-2px) translate(0,-2px)
    60 .socialmedia-buttons img.bounce:hover Property -webkit-transition doesn’t exist : -webkit-transform 0.2s ease-in -webkit-transform 0.2s ease-in
    61 .socialmedia-buttons img.bounce:hover Property -moz-transition doesn’t exist : all 0.2s ease-in all 0.2s ease-in
    62 .socialmedia-buttons img.bounce:hover Property transition doesn’t exist : all 0.2s ease all 0.2s ease
    67 .socialmedia-buttons img.combo:hover Property transform doesn’t exist : translate(0,-4px) translate(0,-4px)
    68 .socialmedia-buttons img.combo:hover Property -moz-transform doesn’t exist : scale(1.1) translate(0,-4px) scale(1.1) translate(0,-4px)
    69 .socialmedia-buttons img.combo:hover Property -webkit-transform doesn’t exist : scale(1.1) translate(0,-4px) scale(1.1) translate(0,-4px)
    70 .socialmedia-buttons img.combo:hover Property -ms-zoom doesn’t exist : 1.1 1.1
    71 .socialmedia-buttons img.combo:hover Property opacity doesn’t exist in CSS level 2.1 but exists in : 1 1
    72 .socialmedia-buttons img.combo:hover Property -moz-opacity doesn’t exist : 1 1
    73 .socialmedia-buttons img.combo:hover Property -webkit-transition doesn’t exist : all 0.2s ease-in all 0.2s ease-in
    74 .socialmedia-buttons img.combo:hover Property -moz-transition doesn’t exist : all 0.2s ease-in all 0.2s ease-in
    75 .socialmedia-buttons img.combo:hover Property transition doesn’t exist : all 0.2s ease all 0.2s ease

Viewing 6 replies - 1 through 6 (of 6 total)
  • brianfreytag

    (@brianfreytag)

    13 years, 3 months ago

    Most of the errors are from my code because of how you’re validating it. You don’t need to fix these validation errors because it’s w3c’s validation scheme that isn’t up to date and doesn’t truly apply CSS3 transitions and stuff like that.

    All of those “errors” are the CSS3 transitions I am using to create the animations you see when you hover over your icons. This is W3C’s fault… not your fault… not my fault… not any of the other plugins that are causing issues.

    Validating CSS is not helpful… What you need to validate is markup.

    Whoever told you “YOU MUST VALIDATE AGAINST W3C” is also a tool. If the website looks perfect in EVERY browser, then you’re fine. Validating is only useful when you’re having trouble with visual appearance in other browsers and don’t know why.

    “Validation Gnomes” are people who get sick joy out of saying “MY STUFF IS W3C COMPLIANT,” but then you find that their site uses old technology. Basic CSS, and very basic XHTML, or they use excessive amounts of client-side scripting like Javascript or Flash, when the same thing can be completed using new CSS3 rules that the W3C validators don’t recognize yet and is more cross-compatible.

    If there is TRUE validation errors (like I’ve taken care of in the past), then I’ll fix it… But I’m not gonna dumb my plugin down so that peoples’ sites will validate with out-of-date rules.

    Thread Starter naturalgirl

    (@naturalgirl)

    13 years, 3 months ago

    Oh alright. I was actually on a site asking about why my links had plummeted in my webmaster tools and some guy told me not to worry about that because its only for page rank. Duh. Thats what I was asking for. Anyway he went on to say that I should really be worried about all the problems with my site not being compliant. He gave me a link to site where I put in my site and it came back with a million errors in xhtml and CSS. I googled what that meant and it said it could stop the search engines from displaying info correctly or something like that. I do get between 5-12 organic searches a day but I thought maybe I would get more if I was compliant. I asked him if the info he gave was even relevant to my question or if this validation matters and he didn’t answer. Thanks for letting me know it is futile and it isn’t necessary. I don’t wanna be bothered with trying to figure it out. Simplicity is the reason I am using a wordpress platform and plugins in the first place.
    ~Smooches~

    brianfreytag

    (@brianfreytag)

    13 years, 3 months ago

    You should definitely resolve your XHTML errors… There are a few that will DEFINITELY hurt your page rankings pretty severly, such as the CDATA problem you have.

    Check your validation at:

    http://validator.w3.org/

    CSS doesn’t affect the Google bot, as they see it just as plain-text anyway. They scan your HTML to make sure it’s valid form. If there are errors, it’ll have issues. There are a couple other things to look at:

    Make sure, on your front page, the website title (“4 Us Naturals”) is in <h1></h1> tags and then the list of articles’ titles are <h2></h2> tags. This shows Google that the title of the website is whatever is in <h1> and then it looks and sees that the articles are <h2>.

    Then on your secondary pages (the actual post) the <h1> tag should be the article title. The website title should just be a <p> or <span> tag.

    These are little things that can help your Google page ranks.

    I’m also very “hit-and-miss” going to your website. Sometimes it loads, sometimes it doesn’t. This will also hurt your Google rankings because if Google bot is trying to get there, but the site doesn’t load…… well you know.

    In short, worry about XHTML markup and ignore CSS markup. The CSS problems I saw when I ran a scan are just old W3C standards that haven’t been updated to reflect CSS3. The XHTML ones will definitely be more of a problem.

    Thread Starter naturalgirl

    (@naturalgirl)

    13 years, 3 months ago

    Not happy to hear that. I think I understand what you are saying about the H1 and H2 tags but I don’t understand how or where to do it and I have no idea what the CDATA thing means. It had about 80+ xhtml errors but I corrected the few I could figure out like all youtube video embeds are not valid. I found someone that found a way to embed without errors. I removed the C from the word c data and it got worse so I added it back until I find out what that is supposed to mean. I might have to pay someone to fix it if I can’t figure it out. It is probably an easy fix. Suggestions?

    brianfreytag

    (@brianfreytag)

    13 years, 3 months ago

    E-mail me:

    brifreytag at gmail dot com

    I’ll work with you a bit.

    But for the CDATA, there is a “<!]” on Line 40 (of your header.php file)… This should be <!]. This might fix it.

    brianfreytag

    (@brianfreytag)

    13 years, 3 months ago

    Sorry.. a

    &lte;!]

    on line 40.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘[Plugin: Social Media Widget] W3C CSS Validator: 28 Errors’ is closed to new replies.