Foro de charlas, amistad, juegos, humor y diversión. ...

quebajamos.li
  • Domain Name
    quebajamos.li
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #59971
  • Page Size
    195.4 KB
  • Ip Address
    108.162.196.181
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    196 GIF, 83 JPG, 77 PNG

Website Meta Analysis

  • Title
    www.QueBajamos.li - Inicio
  • Meta Keyword
    música,libro,libros,noticias,novedades,actualidad,deportes,animales,mascotas,cocina,recetas,cocinar,postres,diseñogràfico,fotografía,fotos,tutoriales,galerìas,talleres,hdd,bluray,dvdrat,dvdfull,dvdrip,dvd,dvdscreener,animación,cartoon,cortometrajes,largometrajes,terror,suspenso,acción,western,hazañas,bèlicas,documentales,videos,videoclips,filmografías,manga,discografías,pop,rock,latino,folcklore,regaeton,hiphop,rap,electrónica,singles,consolas,ebooks,librosvirtuales,audiolibros,lectura,software
  • Meta Description
    Foro de charlas, amistad, juegos, humor y diversión.

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.196.181
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from quebajamos.li.

HTML Analysis

  • server: cloudflare-nginx
  • date: Thu, 10 Oct 2013 02:40:10 GMT
  • content-type: text/html; charset=ISO-8859-1
  • connection: keep-alive
  • x-powered-by: PHP/5.3.16
  • cache-control: private
  • pragma: private
  • x-ua-compatible: IE=7
  • cf-ray: baff1bbf8b60850
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for quebajamos.li

DNS Analysis


DNS servers
ns1.quebajamos.li [95.211.178.229]
ns2.quebajamos.li [95.211.178.229]


DNS Records

Answer records
quebajamos.li MX
preference: 0
exchange: quebajamos.li
14400s
quebajamos.li SOA
server: ns1.quebajamos.li
email: soporte@quebajamos.li
serial: 2013012902
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
quebajamos.li NS  ns2.quebajamos.li 86400s
quebajamos.li NS  ns1.quebajamos.li 86400s
quebajamos.li A 95.211.178.229 14400s

Authority records

Additional records
quebajamos.li A 95.211.178.229 14400s
ns1.quebajamos.li A 95.211.178.229 14400s
ns2.quebajamos.li A 95.211.178.229 14400s

IP 108.162.196.181 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 108.162.196.181"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=108.162.196.181?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 108.162.192.0 - 108.162.255.255
    CIDR: 108.162.192.0/18
    OriginAS: AS13335
    NetName: CLOUDFLARENET
    NetHandle: NET-108-162-192-0-1
    Parent: NET-108-0-0-0-0
    NetType: Direct Assignment
    Comment: http://www.cloudflare.com
    RegDate: 2011-10-28
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-108-162-192-0-1

    OrgName: CloudFlare, Inc.
    OrgId: CLOUD14
    Address: 665 Third Street #207
    City: San Francisco
    StateProv: CA
    PostalCode: 94107
    Country: US
    RegDate: 2010-07-09
    Updated: 2013-01-04
    Comment: http://www.cloudflare.com/
    Ref: http://whois.arin.net/rest/org/CLOUD14

    OrgTechHandle: ADMIN2521-ARIN
    OrgTechName: Admin
    OrgTechPhone: +1-650-319-8930
    OrgTechEmail: admin@cloudflare.com
    OrgTechRef: http://whois.arin.net/rest/poc/ADMIN2521-ARIN

    OrgNOCHandle: NOC11962-ARIN
    OrgNOCName: NOC
    OrgNOCPhone: +1-650-319-8930
    OrgNOCEmail: noc@cloudflare.com
    OrgNOCRef: http://whois.arin.net/rest/poc/NOC11962-ARIN

    OrgAbuseHandle: ABUSE2916-ARIN
    OrgAbuseName: Abuse
    OrgAbusePhone: +1-650-319-8930
    OrgAbuseEmail: abuse@cloudflare.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE2916-ARIN

    RAbuseHandle: ABUSE2916-ARIN
    RAbuseName: Abuse
    RAbusePhone: +1-650-319-8930
    RAbuseEmail: abuse@cloudflare.com
    RAbuseRef: http://whois.arin.net/rest/poc/ABUSE2916-ARIN

    RNOCHandle: NOC11962-ARIN
    RNOCName: NOC
    RNOCPhone: +1-650-319-8930
    RNOCEmail: noc@cloudflare.com
    RNOCRef: http://whois.arin.net/rest/poc/NOC11962-ARIN

    RTechHandle: ADMIN2521-ARIN
    RTechName: Admin
    RTechPhone: +1-650-319-8930
    RTechEmail: admin@cloudflare.com
    RTechRef: http://whois.arin.net/rest/poc/ADMIN2521-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 13 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.6698784101869575
Message Error
  • Error Line 531, Column 74: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …os.li/misc.php?do=cbgoto" method="POST" id="cbgoto" name="cbgoto" target="_bla…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 558, Column 27: character "<" is the first character of a delimiter but occurred as data
    				for (var iCtr=0; iCtr < this.aCybs.length; iCtr++)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 560, Column 80: character "'" is not allowed in the value of attribute "id"
    …e="'+this.aCybs[iCtr].bnrTitle+'" id="'+this.aCybs[iCtr].bnrID+'" style="displ…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 560, Column 174: there is no attribute "valign"
    …D+'" style="display:none;vertical-align:middle;cursor:pointer;" valign="top">';

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 560, Column 179: document type does not allow element "div" here
    …D+'" style="display:none;vertical-align:middle;cursor:pointer;" valign="top">';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 563, Column 391: character "'" is not allowed in the value of attribute "id"
    …'+this.aCybs[iCtr].bnrName+'" id="bnr_'+this.aCybs[iCtr].bnrID+'"><param name=…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 563, Column 650: there is no attribute "src"
    …e="quality" value="high" /><embed src="'+this.aCybs[iCtr].bnrPath+'" quality="…

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 563, Column 689: there is no attribute "quality"
    …'+this.aCybs[iCtr].bnrPath+'" quality="high" width="'+this.aCybs[iCtr].bnrWidt…

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 563, Column 702: there is no attribute "width"
    …iCtr].bnrPath+'" quality="high" width="'+this.aCybs[iCtr].bnrWidth+'" height="…

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 563, Column 741: there is no attribute "height"
    …'+this.aCybs[iCtr].bnrWidth+'" height="'+this.aCybs[iCtr].bnrHeight+'" type="a…

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 563, Column 779: there is no attribute "type"
    …"'+this.aCybs[iCtr].bnrHeight+'" type="application/x-shockwave-flash" pluginsp…

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 563, Column 823: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 563, Column 887: there is no attribute "allowScriptAccess"
    …/go/getflashplayer" allowScriptAccess="sameDomain" flashvars="clickTAG='+this.…

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 563, Column 910: there is no attribute "flashvars"
    …owScriptAccess="sameDomain" flashvars="clickTAG='+this.aCybs[iCtr].bnrURL+'"><…

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 563, Column 948: element "embed" undefined
    …"clickTAG='+this.aCybs[iCtr].bnrURL+'"></embed></object></td><td style="font-f…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 590, Column 26: character "<" is the first character of a delimiter but occurred as data
    				if (this.currentCbnr < this.aCybs.length)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 604, Column 27: character "<" is the first character of a delimiter but occurred as data
    					if (this.currentCbnr < this.aCybs.length - 1)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 744, Column 121: there is no attribute "frameBorder"
    … width="0px" height="0px" frameBorder="0" scrolling="no">Browser not compatibl…

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 751, Column 69: document type does not allow element "form" here
                    <form name="busq" method="get" action="busqueda.php">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 752, Column 20: document type does not allow element "tr" here; assuming missing "table" start-tag
                    <tr><td><input type="text" name="q" placeholder="Busca en QueBa…
  • Error Line 752, Column 65: there is no attribute "placeholder"
    …nput type="text" name="q" placeholder="Busca en QueBajamos" size="50%" require…

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 752, Column 106: "required" is not a member of a group specified for any attribute
    …sca en QueBajamos" size="50%" required></td><td><input type="submit" value="Bu…
  • Error Line 752, Column 111: end tag for "input" omitted, but OMITTAG NO was specified
    …n QueBajamos" size="50%" required></td><td><input type="submit" value="Buscar"…

    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 752, Column 25: start tag was here
                    <tr><td><input type="text" name="q" placeholder="Busca en QueBa…
  • Error Line 753, Column 23: end tag for "table" omitted, but OMITTAG NO was specified
                    </form>

    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 752, Column 17: start tag was here
                    <tr><td><input type="text" name="q" placeholder="Busca en QueBa…
  • Error Line 754, Column 24: end tag for "table" which is not finished
                    </table>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Warning Line 772, Column 36: character "<" is the first character of a delimiter but occurred as data
        for (var i = carousel.first; i <= carousel.last; i++) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 790, Column 69: document type does not allow element "a" here
    …konuid + '" title="' + item.title + '"></a><div style="font-family: Arial; col…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 790, Column 122: document type does not allow element "div" here
    …e="font-family: Arial; color: #4cc8f3;">' + item.title + '</div>').append(img);

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 809, Column 20: there is no attribute "jcarouselindex"
    <li jcarouselindex="1" style="float: left; list-style: none outside none;" clas…

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1009, Column 28: there is no attribute "disabled"
      </ul></div><div disabled="true" style="display: block;" class="jcarousel-prev…

    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 <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Visitor Analysis

Daily Visitor
  • 1.983 visits