Support » Plugins » grins xhtml 1.0 trans not compliant

Viewing 13 replies - 1 through 13 (of 13 total)
  • Try closing the < p > tag before you start DIV on line 115.

    thanks yup, got that error out. i also had to add in a /> to close a tag too. Only ones to get rid of now are :

    Line 122, column 40: character “&” is the first character of a delimiter but occurred as data

    any ideas? thanks.

    btw its the &’s in here it doesnt appear to like :

    if (document.getElementById(‘content’) && document.getElementById(‘content’).type == ‘textarea’) {
    myField = document.getElementById(‘content’);
    }
    else if (document.getElementById(‘comment’) && document.getElementById(‘comment’).type == ‘textarea’) {
    myField = document.getElementById(‘comment’);

    try & amp ; (remove spaces) you should also switch from the wp-online plugin to http://blog.noontide.ca/?p=9 pretty much the same functionalite but the page that display is more standards compliant

    Great, thanks J2000, that worked a treat 🙂

    Pah! – didn’t work for me 🙁

    If I alter the double ampersand the smilies are no longer clickable – although the page then validates faultlessly [it validates with warnings otherwise and the css validator refuses to run]

    The wp-grins call isn’t within any other tags either …stuck! 🙁

    Mark (podz)

    (@podz)

    Support Maven

    It is all okay – check tags above the wp_grins call.
    I had the same issue at first and I can’t recall how I fixed it, but it does work and it is valid

    Damn! [thanks for the quick reply btw]

    I was hoping it was wp-grins! ;P

    I’ve just been through the thing with a fine tooth comb – looking at all the tags and checking with dreamweavers validation tools. What else should I be looking for?

    Mark (podz)

    (@podz)

    Support Maven

    aye! – but not the comments pages: http://cgi.s1mps.plus.com/wordpress/?p=23#comments
    http://validator.w3.org/check?uri=http%3A%2F%2Fcgi.s1mps.plus.com%2Fwordpress%2F%3Fp%3D23
    for example – and it then stalls the css validator

    [really appreciate your help with this btw]

    Mark (podz)

    (@podz)

    Support Maven

    I get that too.
    My xhtml does validate and I put the CSS validator error in parsing the xhtml file as being “one of those things”.

    My xhtml validates
    My CSS validates
    You have the same.

    The CSS validator obviously cannot cope (yet) when mixed.

    Ah – ok. Thanks for your time. I’ll relax then 😛

    Cheers!

    If your javascript is all in a function you simply wrap it in comments and the validator will ignore it:

    <!–
    javascript functions go here
    –>

    Be sure to put them back to proper ampersands, not the encoded ones since javascript won’t know what to do otherwise.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘grins xhtml 1.0 trans not compliant’ is closed to new replies.