SitePoint Sponsor

User Tag List

Results 1 to 5 of 5
  1. #1
    SitePoint Enthusiast
    Join Date
    Sep 2012
    Location
    BD
    Posts
    49
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    CSS validation problems

    Hello everybody,
    I am facing problem with some w3 CSS validation. I need some help for make those css validate with w3 validator. I am giving you guys a link https://www.draculacars.co.uk/index.html please check and help me if you can . I need CSS validation.

    Thank you in advance for help me.

  2. #2
    Mouse catcher silver trophy Stevie D's Avatar
    Join Date
    Mar 2006
    Location
    Yorkshire, UK
    Posts
    5,888
    Mentioned
    122 Post(s)
    Tagged
    1 Thread(s)
    Quote Originally Posted by anturj View Post
    I am facing problem with some w3 CSS validation. I need some help for make those css validate with w3 validator. I am giving you guys a link https://www.draculacars.co.uk/index.html please check and help me if you can . I need CSS validation.
    Looking at the page http://jigsaw.w3.org/css-validator/v....uk/index.html, a number of things strike me.

    The first is that any line that is complaining about a property that starts with -moz-, -o-, -webkit- or -ms- can be pretty much ignored, as all browser-specific properties are non-standard, but as long as they are written in accordance with the specs from the browser manufacturers they will be absolutely fine.

    The second is that bootstrap.min.css is a complete load of garbage. As well as being an advanced case of mammoth bloat, it uses all sorts of non-standard code which looks to me like various hacks, most of which are utter nonsense. Take, for example, the line
    Code:
    .row-fluid .offset8:first-child{margin-left:68.08510638297872%;*margin-left:67.9787234042553%}
    There is no possible reason ever to give a CSS measurement to that level of precision, let alone to provide some browser-specific hack that adjusts it by 0.1%, other than that it was written by someone who is completely clueless.

    A further problem is that because it's been compressed onto a single line and made completely illegible, in the vain hope of shaving a nanosecond or two off the download time, the validator is complaining of every single error being on "line 9", which makes it all but impossible to figure out what it is referring to.

    The best thing you can do with that CSS is to rip it up, throw it in the bin and write the code that you want from scratch.

  3. #3
    SitePoint Enthusiast
    Join Date
    Sep 2012
    Location
    BD
    Posts
    49
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Thank you for help me will you tell me details about your line : The first is that any line that is complaining about a property that starts with -moz-, -o-, -webkit- or -ms- can be pretty much ignored, as all browser-specific properties are non-standard, but as long as they are written in accordance with the specs from the browser manufacturers they will be absolutely fine.

  4. #4
    It's all Geek to me silver trophybronze trophy
    ralph.m's Avatar
    Join Date
    Mar 2009
    Location
    Melbourne, AU
    Posts
    24,203
    Mentioned
    456 Post(s)
    Tagged
    8 Thread(s)
    Quote Originally Posted by anturj View Post
    will you tell me details about your line ...
    There are some experimental features in CSS that—while in development—need to have those "vendor prefixes" attached. They are correct practice, although the validator doesn't officially recognize them (which is silly) so it flags them as a problem. As Stevie said, just ignore the warnings.

  5. #5
    SitePoint Enthusiast
    Join Date
    Sep 2012
    Location
    BD
    Posts
    49
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Thank you ralph


Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •