Your Ad Here

Monday, March 12, 2018

There are 13 bugs in Inoutscripts socialtiles

  1. Warning Line 73, Column 25character "<" is the first character of a delimiter but occurred as data
         if (opera.version()<11){
    This message may appear in several cases:
    • You tried to include the "<" character in your page: you should escape it as "<"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  2. Warning Line 82, Column 17character "<" is the first character of a delimiter but occurred as data
       if (ffversion<5){
    This message may appear in several cases:
    • You tried to include the "<" character in your page: you should escape it as "<"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  3. Warning Line 149, Column 10character "<" is the first character of a delimiter but occurred as data
      if (num<5){
    This message may appear in several cases:
    • You tried to include the "<" character in your page: you should escape it as "<"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  4. Error Line 236, Column 87document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s://shensor.com/social/index.php?page=index/index">
    
The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "" or "") inside an inline element (such as "", "", or "").
  • Error Line 242, Column 52there is no attribute "data-reveal-id"
    …lass="sign_up jpclick" data-reveal-id="myModal" data-animation="none">SignUp</…
    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
  • Error Line 242, Column 77there is no attribute "data-animation"
    …ass="sign_up jpclick" data-reveal-id="myModal" data-animation="none">SignUp
  • You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
  • Error Line 428, Column 163there is no attribute "onSubmit"
    …or.com/social/index.php?page=index/login" onSubmit="return verifyForm_login()">
    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
  • Error Line 437, Column 92there is no attribute "placeholder"
    …name"  id="username"  class="text username_input" placeholder="用户名" value="" />
    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
  • Warning Line 726, Column 9character "<" is the first character of a delimiter but occurred as data
     if (num<5){
    This message may appear in several cases:
    • You tried to include the "<" character in your page: you should escape it as "<"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 772, Column 18character "&" is the first character of a delimiter but occurred as data
     if ( ( !start ) && ( name != document.cookie.substring( 0, name.length ) ) )
    This message may appear in several cases:
    • You tried to include the "<" character in your page: you should escape it as "<"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 772, Column 19character "&" is the first character of a delimiter but occurred as data
     if ( ( !start ) && ( name != document.cookie.substring( 0, name.length ) ) )
    This message may appear in several cases:
    • You tried to include the "<" character in your page: you should escape it as "<"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 802, Column 7end tag for "div" omitted, but OMITTAG NO was specified
  • >
    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
  • Info Line 256, Column 1start tag was here
    <div class="mainBoard">
  • No comments: