voeazul.com.br

Na Azul você encontra passagens mais baratas, pode parcelar em até 10x, viaja em aviões modernos e sem a poltrona do meio. Azul, você lá em cima. Compre e economize! ...

Display Widget for this domain on your website. Click Here
This data was last updated from 04-08-2013 08:10:38  (update).

Overview Info

  • Domain Name
    voeazul.com.br
  • Favicon
  • Alexa Rank
    #12222
  • Google Page Rank
    PR 6
  • Ip Address
    201.77.225.110
  • Page Size
    429.3 KB
  • Images
    2 GIF, 4 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 8 21 1 0 0

Website Meta Analysis



  • Title
    Azul - Linhas Aéreas Brasileiras. Você lá em cima.
  • Meta Keyword
    azul, azul linhas, azul linhas aereas, azul linhas aéreas, cia azul, empresa azul, voe azul, voe azul linhas aereas
  • Meta Description
    Na Azul você encontra passagens mais baratas, pode parcelar em até 10x, viaja em aviões modernos e sem a poltrona do meio. Azul, você lá em cima. Compre e economize!

Technical Analysis



  • Webserver
    Apache-Coyote/1.1
  • Ip Address
    201.77.225.110
  • Domain Age
    4 Years, 10 Months, 20 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from voeazul.com.br.

HTML Analysis

  • server: Apache-Coyote/1.1
  • last-modified: Sat, 03 Aug 2013 02:13:01 GMT
  • content-type: text/html;charset=UTF-8
  • content-encoding: gzip
  • content-length: 50130
  • cache-control: private, max-age=600
  • date: Sun, 04 Aug 2013 20:10:32 GMT
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

% Copyright (c) Nic.br
% The use of the data below is only permitted as described in
% full by the terms of use (http://registro.br/termo/en.html),
% being prohibited its distribution, comercialization or
% reproduction, in particular, to use it for advertising or
% any similar purpose.
% 2012-10-01 09:59:37 (BRT -03:00)

domain: voeazul.com.br
owner: Azul Linhas Aéreas Brasileiras S/A.
ownerid: 009.296.295/0001-60
responsible: Jefferson Elva Santana
country: BR
owner-c: COEAZ
admin-c: COAAZ
tech-c: COTAZ
billing-c: COCAZ
nserver: ns1.voeazul.com.br 201.77.225.118
nsstat: 20120930 AA
nslastaa: 20120930
nserver: ns2.voeazul.com.br 201.77.225.119
nsstat: 20120930 AA
nslastaa: 20120930
nserver: ns3.voeazul.com.br 209.98.120.177
nsstat: 20120930 AA
nslastaa: 20120930
created: 20080327 #4350844
expires: 20140327
changed: 20120510
status: published

nic-hdl-br: COAAZ
person: Contato Administrativo AZUL
e-mail: email
created: 20081128
changed: 20081128

nic-hdl-br: COCAZ
person: Contato Cobrança AZUL
e-mail: email
created: 20081128
changed: 20120510

nic-hdl-br: COEAZ
person: Contato Entidade AZUL
e-mail: email
created: 20081128
changed: 20081128

nic-hdl-br: COTAZ
person: Contato Tecnico AZUL
e-mail: email
created: 20081128
changed: 20081128

% Security and mail abuse issues should also be addressed to
% cert.br, http://www.cert.br/, respectivelly to email
% and email
%
% whois.registro.br accepts only direct match queries. Types
% of queries are: domain (.br), ticket, provider, ID, CIDR
% block, IP and ASN.

IP 201.77.225.110 Analysis

  • Country Code
    BR
  • Country Code3
    BRA
  • Country Name
    Brazil
  • City
    SA
  • Continent Code
    10° South
  • Latitude
    55.
  • Longitude
  • No whois ip data for 201.77.225.110

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 294 Errors
  • 157 Warnings
Ratio Text/Html
  • 0.29669299863753096
Message Error
  • Error Line 45, Column 83: required attribute "alt" not specified
    …g src="https://www.wtp101.com/pixel?id=3143" width="1" height="1" border="0" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 54, Column 125: syntax of attribute value does not conform to declared value
    …/B2BFrontEnd/ConteudoDinamico.aspx' title='Agência' target=''>Agência</a> </li>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 56, Column 102: syntax of attribute value does not conform to declared value
    …://www.voeazul.com.br/fale-conosco' title='Contato' target=''>Contato</a> </li>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 58, Column 137: syntax of attribute value does not conform to declared value
    …aspx?culture=en-US' title='English Version' target=''>English Version</a> </li>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 95, Column 115: end tag for "input" omitted, but OMITTAG NO was specified
    …="bt-limparLogin" value="" name="" class="jqTransformHidden" checked="checked">

    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 95, Column 11: start tag was here
    	        	<input type="checkbox" id="bt-limparLogin" value="" name="" class="jq…
  • Error Line 131, Column 113: syntax of attribute value does not conform to declared value
    …aspx' title='Minhas reservas' target=''>Minhas reservas</a></li><li><a href='h…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 131, Column 237: syntax of attribute value does not conform to declared value
    …spx' title='Check-in On-line' target=''>Check-in On-line</a></li><li><a href='…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 131, Column 364: syntax of attribute value does not conform to declared value
    …n.aspx' title='Status de Voo' target=''>Status de Voo</a></li><li><a href='/se…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 131, Column 437: syntax of attribute value does not conform to declared value
    …='/servicos' title='Serviços' target=''>Serviços</a></li><li><a href='/informa…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 131, Column 523: syntax of attribute value does not conform to declared value
    …a-viajar' title='Informações' target=''>Informações</a></li><li><a href='/novo…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 131, Column 603: syntax of attribute value does not conform to declared value
    …a-azul' title='Novo na Azul?' target=''>Novo na Azul?</a></li><li><a href='/pa…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 131, Column 698: syntax of attribute value does not conform to declared value
    …omocionais' title='Promoções' target=''>Promoções</a></li><li><a href='http://…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 138, Column 81: syntax of attribute value does not conform to declared value
    …l/onibus-azul' title='Ônibus' target=''><span class='ico-bus'></span>Ônibus</a…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 138, Column 235: syntax of attribute value does not conform to declared value
    …' title='Estacionamento Azul' target=''><span class='ico-est'></span>Estaciona…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 138, Column 367: syntax of attribute value does not conform to declared value
    …s-da-azul' title='Lojas Azul' target=''><span class='ico-loja'></span>Lojas Az…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 138, Column 490: syntax of attribute value does not conform to declared value
    …aco-azul' title='Espaço Azul' target=''><span class='ico-espaco'></span>Espaço…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 138, Column 625: syntax of attribute value does not conform to declared value
    …a-azul' title='Assento extra' target=''><span class='ico-assento'></span>Assen…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 138, Column 752: syntax of attribute value does not conform to declared value
    …v-ao-vivo' title='TV ao Vivo' target=''><span class='ico-canal'></span>TV ao V…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 138, Column 864: character "&" is the first character of a delimiter but occurred as data
    …cia-azul/lanches-azul' title='Bebidas & Snacks' target=''><span class='ico-beb…

    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 138, Column 882: syntax of attribute value does not conform to declared value
    …zul' title='Bebidas & Snacks' target=''><span class='ico-bebi'></span>Bebidas …

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 138, Column 922: character "&" is the first character of a delimiter but occurred as data
    …<span class='ico-bebi'></span>Bebidas & Snacks</a></li><li><a href='/experienc…

    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 138, Column 1023: syntax of attribute value does not conform to declared value
    …ra' title='Reserva em espera' target=''><span class='ico-reserva'></span>Reser…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 138, Column 1182: syntax of attribute value does not conform to declared value
    …l' title='Assistência Viagem' target=''><span class='ico-assistencia'></span>A…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 145, Column 69: syntax of attribute value does not conform to declared value
    …re-azul' title='Sobre a Azul' target=''>Sobre a Azul</a></li><li><a href='/map…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 145, Column 148: syntax of attribute value does not conform to declared value
    …-rotas' title='Mapa de Rotas' target=''>Mapa de Rotas</a></li><li><a href='htt…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 145, Column 634: syntax of attribute value does not conform to declared value
    …asp' title='Trabalhe na Azul' target=''>Trabalhe na Azul</a></li><li><a href='…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 145, Column 740: syntax of attribute value does not conform to declared value
    …tle='Política de Privacidade' target=''>Política de Privacidade</a></li><li><a…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 145, Column 847: syntax of attribute value does not conform to declared value
    … title='Perguntas Frequentes' target=''>Perguntas Frequentes</a></li><li><a hr…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 145, Column 934: syntax of attribute value does not conform to declared value
    … title='Academia de Serviços' target=''>Academia de Serviços</a></li><li><a hr…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 145, Column 1020: syntax of attribute value does not conform to declared value
    …i><li><a href='/azul-e-trip' title='Azul e Trip' target=''>Azul e Trip</a></li>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 166, Column 179: document type does not allow element "iframe" here
    … a + '?" width="1" height="1" frameborder="0" style="display:none"></iframe>');

    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 177, Column 110: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …tle="Passagens a&eacute;reas Azul"><h2>Passagens a&eacute;reas Azul</h2></a></…

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 178, Column 112: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …viagem" title="Hot&eacute;is e Carros"><h2>Hot&eacute;is e Carros</h2></a></li>

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 179, Column 103: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ass="minhas-reservas" title="Minhas reservas"><h2>Minhas reservas</h2></a></li>

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 180, Column 101: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …lass="web-check-in" title="Check-in On-line"><h2>Check-in On-line</h2></a></li>

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 181, Column 135: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …px' class="status-de-voo" title="Status de Voo"><h2>Status de Voo</h2></a></li>

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 207, Column 161: required attribute "alt" not specified
    …p;blobtable=MungoBlobs&amp;blobwhere=1318893745342&amp;ssbinary=true' /> </div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 209, Column 31: required attribute "type" not specified
    <script language="javascript" >

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 213, Column 12: character "&" is the first character of a delimiter but occurred as data
    		if(email && email != ""){

    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 213, Column 13: character "&" is the first character of a delimiter but occurred as data
    		if(email && email != ""){

    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 232, Column 19: character "&" is the first character of a delimiter but occurred as data
    		      		if(data && data != "" && data.status == "ok"){

    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 232, Column 20: character "&" is the first character of a delimiter but occurred as data
    		      		if(data && data != "" && data.status == "ok"){

    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 232, Column 33: character "&" is the first character of a delimiter but occurred as data
    		      		if(data && data != "" && data.status == "ok"){

    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 232, Column 34: character "&" is the first character of a delimiter but occurred as data
    		      		if(data && data != "" && data.status == "ok"){

    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 253, Column 31: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    	<form action="#" method="POST" id="contato">

    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.

  • Error Line 266, Column 10: required attribute "type" not specified
    		<script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 271, Column 58: cannot generate system identifier for general entity "appId"
    			js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=121870827916569";

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 271, Column 58: general entity "appId" not defined and no default entity
    			js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=121870827916569";

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 271, Column 63: reference not terminated by REFC delimiter
    			js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=121870827916569";

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 271, Column 63: reference to entity "appId" for which no system identifier could be generated
    			js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=121870827916569";

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 271, Column 57: entity was defined here
    			js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=121870827916569";
  • Error Line 274, Column 34: there is no attribute "data-href"
    		<div class="fb-like" data-href="http://www.facebook.com/AzulLinhasAereas" dat…

    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 274, Column 87: there is no attribute "data-send"
    …ebook.com/AzulLinhasAereas" data-send="false" data-layout="button_count" data-…

    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 274, Column 107: there is no attribute "data-layout"
    …Aereas" data-send="false" data-layout="button_count" data-width="450" data-sho…

    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 274, Column 133: there is no attribute "data-width"
    …lse" data-layout="button_count" data-width="450" data-show-faces="false"></div>

    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 274, Column 155: there is no attribute "data-show-faces"
    …lse" data-layout="button_count" data-width="450" data-show-faces="false"></div>

    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 317, Column 134: syntax of attribute value does not conform to declared value
    …ns.com.br' title='Saiba mais' target=''>Saiba mais</a></li></ol><p><strong>Pac…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 322, Column 46: cannot generate system identifier for general entity "blobkey"
    … src='../ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwher…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 322, Column 46: general entity "blobkey" not defined and no default entity
    … src='../ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwher…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 322, Column 53: reference not terminated by REFC delimiter
    …./ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 322, Column 53: reference to external entity in attribute value
    …./ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 322, Column 53: reference to entity "blobkey" for which no system identifier could be generated
    …./ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 45: entity was defined here
    …g src='../ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 322, Column 57: cannot generate system identifier for general entity "blobtable"
    …/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=131889372…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 322, Column 57: general entity "blobtable" not defined and no default entity
    …/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=131889372…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 322, Column 66: reference not terminated by REFC delimiter
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893722447&ssbi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 322, Column 66: reference to external entity in attribute value
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893722447&ssbi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 322, Column 66: reference to entity "blobtable" for which no system identifier could be generated
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893722447&ssbi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 56: entity was defined here
    …s/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188937…
  • Warning Line 322, Column 78: cannot generate system identifier for general entity "blobwhere"
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' a…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 322, Column 78: general entity "blobwhere" not defined and no default entity
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' a…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 322, Column 87: reference not terminated by REFC delimiter
    …bkey=id&blobtable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' alt='Carna…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 322, Column 87: reference to external entity in attribute value
    …bkey=id&blobtable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' alt='Carna…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 322, Column 87: reference to entity "blobwhere" for which no system identifier could be generated
    …bkey=id&blobtable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' alt='Carna…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 77: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' …
  • Warning Line 322, Column 102: cannot generate system identifier for general entity "ssbinary"
    …btable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' alt='Carnaval 2013' />

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 322, Column 102: general entity "ssbinary" not defined and no default entity
    …btable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' alt='Carnaval 2013' />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 322, Column 110: reference not terminated by REFC delimiter
    …btable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' alt='Carnaval 2013' />

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 322, Column 110: reference to external entity in attribute value
    …btable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' alt='Carnaval 2013' />

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 322, Column 110: reference to entity "ssbinary" for which no system identifier could be generated
    …btable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' alt='Carnaval 2013' />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 101: entity was defined here
    …btable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' alt='Carnaval 2013' />
  • Warning Line 346, Column 73: cannot generate system identifier for general entity "specialid"
    …com.br/travel/specials.cfm?track=8606&specialid=941' title='Fernando de Noronh…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 346, Column 73: general entity "specialid" not defined and no default entity
    …com.br/travel/specials.cfm?track=8606&specialid=941' title='Fernando de Noronh…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 346, Column 82: reference not terminated by REFC delimiter
    …avel/specials.cfm?track=8606&specialid=941' title='Fernando de Noronha' target…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 346, Column 82: reference to external entity in attribute value
    …avel/specials.cfm?track=8606&specialid=941' title='Fernando de Noronha' target…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 346, Column 82: reference to entity "specialid" for which no system identifier could be generated
    …avel/specials.cfm?track=8606&specialid=941' title='Fernando de Noronha' target…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 346, Column 72: entity was defined here
    ….com.br/travel/specials.cfm?track=8606&specialid=941' title='Fernando de Noron…
  • Warning Line 347, Column 53: reference not terminated by REFC delimiter
    …./ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 347, Column 53: reference to external entity in attribute value
    …./ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 347, Column 53: reference to entity "blobkey" for which no system identifier could be generated
    …./ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 45: entity was defined here
    …g src='../ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 347, Column 66: reference not terminated by REFC delimiter
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893690931&ssbi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 347, Column 66: reference to external entity in attribute value
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893690931&ssbi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 347, Column 66: reference to entity "blobtable" for which no system identifier could be generated
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893690931&ssbi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 56: entity was defined here
    …s/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188937…
  • Warning Line 347, Column 87: reference not terminated by REFC delimiter
    …bkey=id&blobtable=MungoBlobs&blobwhere=1318893690931&ssbinary=true' alt='Ferna…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 347, Column 87: reference to external entity in attribute value
    …bkey=id&blobtable=MungoBlobs&blobwhere=1318893690931&ssbinary=true' alt='Ferna…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 347, Column 87: reference to entity "blobwhere" for which no system identifier could be generated
    …bkey=id&blobtable=MungoBlobs&blobwhere=1318893690931&ssbinary=true' alt='Ferna…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 77: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' …
  • Warning Line 347, Column 110: reference not terminated by REFC delimiter
    …=MungoBlobs&blobwhere=1318893690931&ssbinary=true' alt='Fernando de Noronha' />

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 347, Column 110: reference to external entity in attribute value
    …=MungoBlobs&blobwhere=1318893690931&ssbinary=true' alt='Fernando de Noronha' />

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 347, Column 110: reference to entity "ssbinary" for which no system identifier could be generated
    …=MungoBlobs&blobwhere=1318893690931&ssbinary=true' alt='Fernando de Noronha' />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 101: entity was defined here
    …btable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' alt='Carnaval 2013' />
  • Warning Line 349, Column 94: reference not terminated by REFC delimiter
    …avel/specials.cfm?track=8606&specialid=941' class="more-red" title="Saiba Mais…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 349, Column 94: reference to external entity in attribute value
    …avel/specials.cfm?track=8606&specialid=941' class="more-red" title="Saiba Mais…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 349, Column 94: reference to entity "specialid" for which no system identifier could be generated
    …avel/specials.cfm?track=8606&specialid=941' class="more-red" title="Saiba Mais…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 346, Column 72: entity was defined here
    ….com.br/travel/specials.cfm?track=8606&specialid=941' title='Fernando de Noron…
  • Warning Line 352, Column 82: reference not terminated by REFC delimiter
    …avel/specials.cfm?track=8606&specialid=941' title='Pousadas Domiciliares' targ…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 352, Column 82: reference to external entity in attribute value
    …avel/specials.cfm?track=8606&specialid=941' title='Pousadas Domiciliares' targ…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 352, Column 82: reference to entity "specialid" for which no system identifier could be generated
    …avel/specials.cfm?track=8606&specialid=941' title='Pousadas Domiciliares' targ…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 346, Column 72: entity was defined here
    ….com.br/travel/specials.cfm?track=8606&specialid=941' title='Fernando de Noron…
  • Warning Line 356, Column 83: reference not terminated by REFC delimiter
    …avel/specials.cfm?track=8606&specialid=941' title='Café da manhã - Passagem aé…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 356, Column 83: reference to external entity in attribute value
    …avel/specials.cfm?track=8606&specialid=941' title='Café da manhã - Passagem aé…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 356, Column 83: reference to entity "specialid" for which no system identifier could be generated
    …avel/specials.cfm?track=8606&specialid=941' title='Café da manhã - Passagem aé…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 346, Column 72: entity was defined here
    ….com.br/travel/specials.cfm?track=8606&specialid=941' title='Fernando de Noron…
  • Warning Line 372, Column 53: reference not terminated by REFC delimiter
    …./ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 372, Column 53: reference to external entity in attribute value
    …./ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 372, Column 53: reference to entity "blobkey" for which no system identifier could be generated
    …./ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 45: entity was defined here
    …g src='../ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 372, Column 66: reference not terminated by REFC delimiter
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893722432&ssbi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 372, Column 66: reference to external entity in attribute value
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893722432&ssbi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 372, Column 66: reference to entity "blobtable" for which no system identifier could be generated
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893722432&ssbi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 56: entity was defined here
    …s/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188937…
  • Warning Line 372, Column 87: reference not terminated by REFC delimiter
    …bkey=id&blobtable=MungoBlobs&blobwhere=1318893722432&ssbinary=true' alt='Ilhéu…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 372, Column 87: reference to external entity in attribute value
    …bkey=id&blobtable=MungoBlobs&blobwhere=1318893722432&ssbinary=true' alt='Ilhéu…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 372, Column 87: reference to entity "blobwhere" for which no system identifier could be generated
    …bkey=id&blobtable=MungoBlobs&blobwhere=1318893722432&ssbinary=true' alt='Ilhéu…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 77: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' …
  • Warning Line 372, Column 110: reference not terminated by REFC delimiter
    …=id&blobtable=MungoBlobs&blobwhere=1318893722432&ssbinary=true' alt='Ilhéus' />

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 372, Column 110: reference to external entity in attribute value
    …=id&blobtable=MungoBlobs&blobwhere=1318893722432&ssbinary=true' alt='Ilhéus' />

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 372, Column 110: reference to entity "ssbinary" for which no system identifier could be generated
    …=id&blobtable=MungoBlobs&blobwhere=1318893722432&ssbinary=true' alt='Ilhéus' />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 101: entity was defined here
    …btable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' alt='Carnaval 2013' />
  • Warning Line 397, Column 82: reference not terminated by REFC delimiter
    …avel/specials.cfm?track=8606&specialid=494' title='Foz do Iguaçu' target="_bla…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 397, Column 82: reference to external entity in attribute value
    …avel/specials.cfm?track=8606&specialid=494' title='Foz do Iguaçu' target="_bla…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 397, Column 82: reference to entity "specialid" for which no system identifier could be generated
    …avel/specials.cfm?track=8606&specialid=494' title='Foz do Iguaçu' target="_bla…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 346, Column 72: entity was defined here
    ….com.br/travel/specials.cfm?track=8606&specialid=941' title='Fernando de Noron…
  • Warning Line 398, Column 53: reference not terminated by REFC delimiter
    …./ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 398, Column 53: reference to external entity in attribute value
    …./ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 398, Column 53: reference to entity "blobkey" for which no system identifier could be generated
    …./ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 45: entity was defined here
    …g src='../ss/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 398, Column 66: reference not terminated by REFC delimiter
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893686906&ssbi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 398, Column 66: reference to external entity in attribute value
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893686906&ssbi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 398, Column 66: reference to entity "blobtable" for which no system identifier could be generated
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893686906&ssbi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 56: entity was defined here
    …s/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13188937…
  • Warning Line 398, Column 87: reference not terminated by REFC delimiter
    …bkey=id&blobtable=MungoBlobs&blobwhere=1318893686906&ssbinary=true' alt='Foz d…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 398, Column 87: reference to external entity in attribute value
    …bkey=id&blobtable=MungoBlobs&blobwhere=1318893686906&ssbinary=true' alt='Foz d…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 398, Column 87: reference to entity "blobwhere" for which no system identifier could be generated
    …bkey=id&blobtable=MungoBlobs&blobwhere=1318893686906&ssbinary=true' alt='Foz d…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 77: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' …
  • Warning Line 398, Column 110: reference not terminated by REFC delimiter
    …btable=MungoBlobs&blobwhere=1318893686906&ssbinary=true' alt='Foz do Iguaçu' />

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 398, Column 110: reference to external entity in attribute value
    …btable=MungoBlobs&blobwhere=1318893686906&ssbinary=true' alt='Foz do Iguaçu' />

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 398, Column 110: reference to entity "ssbinary" for which no system identifier could be generated
    …btable=MungoBlobs&blobwhere=1318893686906&ssbinary=true' alt='Foz do Iguaçu' />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 322, Column 101: entity was defined here
    …btable=MungoBlobs&blobwhere=1318893722447&ssbinary=true' alt='Carnaval 2013' />
  • Warning Line 400, Column 94: reference not terminated by REFC delimiter
    …avel/specials.cfm?track=8606&specialid=494' class="more-red" title="Saiba Mais…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 400, Column 94: reference to external entity in attribute value
    …avel/specials.cfm?track=8606&specialid=494' class="more-red" title="Saiba Mais…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 400, Column 94: reference to entity "specialid" for which no system identifier could be generated
    …avel/specials.cfm?track=8606&specialid=494' class="more-red" title="Saiba Mais…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 346, Column 72: entity was defined here
    ….com.br/travel/specials.cfm?track=8606&specialid=941' title='Fernando de Noron…
  • Warning Line 403, Column 82: reference not terminated by REFC delimiter
    …avel/specials.cfm?track=8606&specialid=494' title='Foz Plaza Hotel' target="_b…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 403, Column 82: reference to external entity in attribute value
    …avel/specials.cfm?track=8606&specialid=494' title='Foz Plaza Hotel' target="_b…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 403, Column 82: reference to entity "specialid" for which no system identifier could be generated
    …avel/specials.cfm?track=8606&specialid=494' title='Foz Plaza Hotel' target="_b…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 346, Column 72: entity was defined here
    ….com.br/travel/specials.cfm?track=8606&specialid=941' title='Fernando de Noron…
  • Warning Line 407, Column 83: reference not terminated by REFC delimiter
    …avel/specials.cfm?track=8606&specialid=494' title='Café da manhã – Passagem aé…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 407, Column 83: reference to external entity in attribute value
    …avel/specials.cfm?track=8606&specialid=494' title='Café da manhã – Passagem aé…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 407, Column 83: reference to entity "specialid" for which no system identifier could be generated
    …avel/specials.cfm?track=8606&specialid=494' title='Café da manhã – Passagem aé…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 346, Column 72: entity was defined here
    ….com.br/travel/specials.cfm?track=8606&specialid=941' title='Fernando de Noron…
  • Error Line 479, Column 44: end tag for "ul" which is not finished
                	<ul id="ulBuscasRecentes"></ul>

    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.

  • Error Line 486, Column 108: end tag for "input" omitted, but OMITTAG NO was specified
    …e="checkbox" id="bt-naoSalvarBusca" value="" name="" class="jqTransformHidden">

    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 486, Column 19: start tag was here
    	              			<input type="checkbox" id="bt-naoSalvarBusca" value="" name="…
  • Error Line 503, Column 37: ID "grupo1" already defined
              		<input type="radio" id="grupo1" name="ControlGroupSearchView2$Avail…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 496, Column 30: ID "grupo1" first defined here
    					<input type="radio" id="grupo1" name="ControlGroupSearchView2$Availability…
  • Error Line 509, Column 37: ID "grupo1" already defined
              		<input type="radio" id="grupo1" name="ControlGroupSearchView2$Avail…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 496, Column 30: ID "grupo1" first defined here
    					<input type="radio" id="grupo1" name="ControlGroupSearchView2$Availability…
  • Error Line 524, Column 98: there is no attribute "autocomplete"
    …rmdone jqTransformInput" autocomplete="off" onkeyup="comboAzul.buscar('txtBusc…

    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 550, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 567, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 605, Column 16: there is no attribute "index"
    		<li><a index="0" href="#" class="selected">1</a></li>

    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 772, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 823, Column 18: ID "Adulto1" already defined
    	    <select id="Adulto1" name='ControlGroupSearchView2$AvailabilitySearchInput…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 617, Column 18: ID "Adulto1" first defined here
    	    <select id="Adulto1" name='ControlGroupSearchView2$AvailabilitySearchInput…
  • Error Line 865, Column 15: ID "crianca1" already defined
    		<select id="crianca1" name='ControlGroupSearchView2$AvailabilitySearchInputSe…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 659, Column 15: ID "crianca1" first defined here
    		<select id="crianca1" name='ControlGroupSearchView2$AvailabilitySearchInputSe…
  • Error Line 908, Column 15: ID "bebes1" already defined
    		<select id="bebes1" name='ControlGroupSearchView2$AvailabilitySearchInputSear…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 702, Column 15: ID "bebes1" first defined here
    		<select id="bebes1" name='ControlGroupSearchView2$AvailabilitySearchInputSear…
  • Error Line 979, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1023, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1076, Column 18: ID "Adulto1" already defined
    	    <select id="Adulto1" name='ControlGroupSearchView2$AvailabilitySearchInput…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 617, Column 18: ID "Adulto1" first defined here
    	    <select id="Adulto1" name='ControlGroupSearchView2$AvailabilitySearchInput…
  • Error Line 1118, Column 15: ID "crianca1" already defined
    		<select id="crianca1" name='ControlGroupSearchView2$AvailabilitySearchInputSe…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 659, Column 15: ID "crianca1" first defined here
    		<select id="crianca1" name='ControlGroupSearchView2$AvailabilitySearchInputSe…
  • Error Line 1161, Column 15: ID "bebes1" already defined
    		<select id="bebes1" name='ControlGroupSearchView2$AvailabilitySearchInputSear…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 702, Column 15: ID "bebes1" first defined here
    		<select id="bebes1" name='ControlGroupSearchView2$AvailabilitySearchInputSear…
  • Error Line 1242, Column 51: ID "grupo2" already defined
    …<input type="radio" name="grupo2" id="grupo2" value="HotelCarro" class="jqTran…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1235, Column 51: ID "grupo2" first defined here
    …<input type="radio" name="grupo2" id="grupo2" value="aerioHotelTraslados"  che…
  • Error Line 1249, Column 51: ID "grupo2" already defined
    …<input type="radio" name="grupo2" id="grupo2" value="Hotel" class="jqTransform…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1235, Column 51: ID "grupo2" first defined here
    …<input type="radio" name="grupo2" id="grupo2" value="aerioHotelTraslados"  che…
  • Error Line 1256, Column 51: ID "grupo2" already defined
    …<input type="radio" name="grupo2" id="grupo2" value="Carro" class="jqTransform…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1235, Column 51: ID "grupo2" first defined here
    …<input type="radio" name="grupo2" id="grupo2" value="aerioHotelTraslados"  che…
  • Error Line 1264, Column 51: ID "grupo2" already defined
    …<input type="radio" name="grupo2" id="grupo2" value="TrasladosPasseios" class=…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1235, Column 51: ID "grupo2" first defined here
    …<input type="radio" name="grupo2" id="grupo2" value="aerioHotelTraslados"  che…
  • Error Line 1269, Column 89: value of attribute "method" cannot be "GET"; must be one of "get", "post"
    …w.azultravel.com.br/travel/arc_waiting.cfm " method="GET" id="pacoteaereoform">

    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.

  • Error Line 1270, Column 58: end tag for "input" omitted, but OMITTAG NO was specified
            	<input type="hidden" name="search" value="true">

    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 1270, Column 10: start tag was here
            	<input type="hidden" name="search" value="true">
  • Error Line 1271, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="hidden" name="air1" value="true">

    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 1271, Column 4: start tag was here
    			<input type="hidden" name="air1" value="true">
  • Error Line 1272, Column 51: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="hidden" name="room1" value="true">

    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 1272, Column 4: start tag was here
    			<input type="hidden" name="room1" value="true">
  • Error Line 1274, Column 55: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="hidden" name="roundtrip" value="true">

    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 1274, Column 4: start tag was here
    			<input type="hidden" name="roundtrip" value="true">
  • Error Line 1302, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1306, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
    								"jqtranformdone jqTransformInput" style="width: 80px;">

    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 1305, Column 9: start tag was here
    								<input size="8"  type="text" value="" id="from2" name="date1" class=
  • Error Line 1315, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1319, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
    								"jqtranformdone jqTransformInput" style="width: 80px;">

    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 1318, Column 9: start tag was here
    								<input size="8" type="text" value="" id="to2" name="date2" class=
  • Error Line 1372, Column 19: ID "chegada" already defined
    		   	<select id="chegada" name='time2' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1345, Column 19: ID "chegada" first defined here
    		   	<select id="chegada" name='time1' class="jqTransformHidden">
  • Error Line 1434, Column 18: ID "Adulto1" already defined
    	    <select id="Adulto1" name='adults' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 617, Column 18: ID "Adulto1" first defined here
    	    <select id="Adulto1" name='ControlGroupSearchView2$AvailabilitySearchInput…
  • Error Line 1523, Column 99: end tag for "input" omitted, but OMITTAG NO was specified
    …dio" checked="checked" name="infant1" value="in_lap" class="jqTransformHidden">

    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 1523, Column 5: start tag was here
    				<input type="radio" checked="checked" name="infant1" value="in_lap" class="…
  • Error Line 1530, Column 82: end tag for "input" omitted, but OMITTAG NO was specified
    …		<input type="radio" name="infant1" value="in_seat" class="jqTransformHidden">

    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 1530, Column 5: start tag was here
    				<input type="radio" name="infant1" value="in_seat" class="jqTransformHidden…
  • Error Line 1581, Column 99: end tag for "input" omitted, but OMITTAG NO was specified
    …dio" checked="checked" name="infant2" value="in_lap" class="jqTransformHidden">

    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 1581, Column 5: start tag was here
    				<input type="radio" checked="checked" name="infant2" value="in_lap" class="…
  • Error Line 1588, Column 82: end tag for "input" omitted, but OMITTAG NO was specified
    …		<input type="radio" name="infant2" value="in_seat" class="jqTransformHidden">

    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 1588, Column 5: start tag was here
    				<input type="radio" name="infant2" value="in_seat" class="jqTransformHidden…
  • Error Line 1634, Column 99: end tag for "input" omitted, but OMITTAG NO was specified
    …dio" checked="checked" name="infant3" value="in_lap" class="jqTransformHidden">

    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 1634, Column 5: start tag was here
    				<input type="radio" checked="checked" name="infant3" value="in_lap" class="…
  • Error Line 1641, Column 82: end tag for "input" omitted, but OMITTAG NO was specified
    …		<input type="radio" name="infant3" value="in_seat" class="jqTransformHidden">

    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 1641, Column 5: start tag was here
    				<input type="radio" name="infant3" value="in_seat" class="jqTransformHidden…
  • Error Line 1663, Column 55: end tag for "input" omitted, but OMITTAG NO was specified
    	    	<input type="hidden" name="search" value="true">

    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 1663, Column 7: start tag was here
    	    	<input type="hidden" name="search" value="true">
  • Error Line 1664, Column 51: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="hidden" name="room1" value="true">

    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 1664, Column 4: start tag was here
    			<input type="hidden" name="room1" value="true">
  • Error Line 1665, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="hidden" name="car1" value="true">

    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 1665, Column 4: start tag was here
    			<input type="hidden" name="car1" value="true">
  • Error Line 1667, Column 55: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="hidden" name="roundtrip" value="true">

    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 1667, Column 4: start tag was here
    			<input type="hidden" name="roundtrip" value="true">
  • Error Line 1685, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1688, Column 131: end tag for "input" omitted, but OMITTAG NO was specified
    …="date1" size="8" class="jqtranformdone jqTransformInput" style="width: 80px;">

    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 1688, Column 9: start tag was here
    								<input type="text" id="from3" value="" name="date1" size="8" class="jqt…
  • Error Line 1698, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1702, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
    								"jqtranformdone jqTransformInput" style="width: 80px;">

    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 1701, Column 9: start tag was here
    								<input type="text" id="to3" name="date2" value="" size="8" class=
  • Error Line 1796, Column 19: ID "chegada" already defined
    		    <select id="chegada" name='time1' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1345, Column 19: ID "chegada" first defined here
    		   	<select id="chegada" name='time1' class="jqTransformHidden">
  • Error Line 1866, Column 19: ID "chegada" already defined
    		    <select id="chegada" name='time2' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1345, Column 19: ID "chegada" first defined here
    		   	<select id="chegada" name='time1' class="jqTransformHidden">
  • Error Line 1913, Column 19: ID "Apartamento1" already defined
    		    <select id="Apartamento1" name='num_rooms' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1399, Column 19: ID "Apartamento1" first defined here
    		    <select id="Apartamento1" name='num_rooms' class="jqTransformHidden">
  • Error Line 1948, Column 18: ID "Adulto1" already defined
    	    <select id="Adulto1" name='adults' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 617, Column 18: ID "Adulto1" first defined here
    	    <select id="Adulto1" name='ControlGroupSearchView2$AvailabilitySearchInput…
  • Error Line 1979, Column 22: ID "crianca4" already defined
    	        <select id="crianca4" name='dynamic_children' class="criancas jqTransf…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1465, Column 22: ID "crianca4" first defined here
    	        <select id="crianca4" name='dynamic_children' class="criancas jqTransf…
  • Error Line 2037, Column 99: end tag for "input" omitted, but OMITTAG NO was specified
    …dio" checked="checked" name="infant1" value="in_lap" class="jqTransformHidden">

    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 2037, Column 5: start tag was here
    				<input type="radio" checked="checked" name="infant1" value="in_lap" class="…
  • Error Line 2044, Column 82: end tag for "input" omitted, but OMITTAG NO was specified
    …		<input type="radio" name="infant1" value="in_seat" class="jqTransformHidden">

    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 2044, Column 5: start tag was here
    				<input type="radio" name="infant1" value="in_seat" class="jqTransformHidden…
  • Error Line 2095, Column 99: end tag for "input" omitted, but OMITTAG NO was specified
    …dio" checked="checked" name="infant2" value="in_lap" class="jqTransformHidden">

    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 2095, Column 5: start tag was here
    				<input type="radio" checked="checked" name="infant2" value="in_lap" class="…
  • Error Line 2102, Column 82: end tag for "input" omitted, but OMITTAG NO was specified
    …		<input type="radio" name="infant2" value="in_seat" class="jqTransformHidden">

    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 2102, Column 5: start tag was here
    				<input type="radio" name="infant2" value="in_seat" class="jqTransformHidden…
  • Error Line 2148, Column 99: end tag for "input" omitted, but OMITTAG NO was specified
    …dio" checked="checked" name="infant3" value="in_lap" class="jqTransformHidden">

    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 2148, Column 5: start tag was here
    				<input type="radio" checked="checked" name="infant3" value="in_lap" class="…
  • Error Line 2155, Column 82: end tag for "input" omitted, but OMITTAG NO was specified
    …		<input type="radio" name="infant3" value="in_seat" class="jqTransformHidden">

    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 2155, Column 5: start tag was here
    				<input type="radio" name="infant3" value="in_seat" class="jqTransformHidden…
  • Error Line 2178, Column 55: end tag for "input" omitted, but OMITTAG NO was specified
    	    	<input type="hidden" name="search" value="true">

    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 2178, Column 7: start tag was here
    	    	<input type="hidden" name="search" value="true">
  • Error Line 2179, Column 51: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="hidden" name="room1" value="true">

    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 2179, Column 4: start tag was here
    			<input type="hidden" name="room1" value="true">
  • Error Line 2181, Column 56: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="hidden" name="roundtrip" value="false">

    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 2181, Column 4: start tag was here
    			<input type="hidden" name="roundtrip" value="false">
  • Error Line 2199, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 2203, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
    								"jqtranformdone jqTransformInput" style="width: 80px;">

    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 2202, Column 9: start tag was here
    								<input type="text" id="from4" name="date1" value="" size="8" class=
  • Error Line 2212, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 2216, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
    								"jqtranformdone jqTransformInput" style="width: 80px;">

    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 2215, Column 9: start tag was here
    								<input type="text" id="to4" name="date2" value="" size="8" class=
  • Error Line 2242, Column 19: ID "chegada" already defined
    		   	<select id="chegada" name='time1' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1345, Column 19: ID "chegada" first defined here
    		   	<select id="chegada" name='time1' class="jqTransformHidden">
  • Error Line 2269, Column 19: ID "chegada" already defined
    		   	<select id="chegada" name='time2' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1345, Column 19: ID "chegada" first defined here
    		   	<select id="chegada" name='time1' class="jqTransformHidden">
  • Error Line 2296, Column 19: ID "Apartamento1" already defined
    		    <select id="Apartamento1" name='num_rooms' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1399, Column 19: ID "Apartamento1" first defined here
    		    <select id="Apartamento1" name='num_rooms' class="jqTransformHidden">
  • Error Line 2331, Column 18: ID "Adulto1" already defined
    	    <select id="Adulto1" name='adults' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 617, Column 18: ID "Adulto1" first defined here
    	    <select id="Adulto1" name='ControlGroupSearchView2$AvailabilitySearchInput…
  • Error Line 2362, Column 22: ID "crianca4" already defined
    	        <select id="crianca4" name='dynamic_children' class="criancas jqTransf…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1465, Column 22: ID "crianca4" first defined here
    	        <select id="crianca4" name='dynamic_children' class="criancas jqTransf…
  • Error Line 2420, Column 99: end tag for "input" omitted, but OMITTAG NO was specified
    …dio" checked="checked" name="infant1" value="in_lap" class="jqTransformHidden">

    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 2420, Column 5: start tag was here
    				<input type="radio" checked="checked" name="infant1" value="in_lap" class="…
  • Error Line 2427, Column 82: end tag for "input" omitted, but OMITTAG NO was specified
    …		<input type="radio" name="infant1" value="in_seat" class="jqTransformHidden">

    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 2427, Column 5: start tag was here
    				<input type="radio" name="infant1" value="in_seat" class="jqTransformHidden…
  • Error Line 2478, Column 99: end tag for "input" omitted, but OMITTAG NO was specified
    …dio" checked="checked" name="infant2" value="in_lap" class="jqTransformHidden">

    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 2478, Column 5: start tag was here
    				<input type="radio" checked="checked" name="infant2" value="in_lap" class="…
  • Error Line 2485, Column 82: end tag for "input" omitted, but OMITTAG NO was specified
    …		<input type="radio" name="infant2" value="in_seat" class="jqTransformHidden">

    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 2485, Column 5: start tag was here
    				<input type="radio" name="infant2" value="in_seat" class="jqTransformHidden…
  • Error Line 2531, Column 99: end tag for "input" omitted, but OMITTAG NO was specified
    …dio" checked="checked" name="infant3" value="in_lap" class="jqTransformHidden">

    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 2531, Column 5: start tag was here
    				<input type="radio" checked="checked" name="infant3" value="in_lap" class="…
  • Error Line 2538, Column 82: end tag for "input" omitted, but OMITTAG NO was specified
    …		<input type="radio" name="infant3" value="in_seat" class="jqTransformHidden">

    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 2538, Column 5: start tag was here
    				<input type="radio" name="infant3" value="in_seat" class="jqTransformHidden…
  • Error Line 2560, Column 55: end tag for "input" omitted, but OMITTAG NO was specified
    	    	<input type="hidden" name="search" value="true">

    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 2560, Column 7: start tag was here
    	    	<input type="hidden" name="search" value="true">
  • Error Line 2561, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="hidden" name="car1" value="true">

    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 2561, Column 4: start tag was here
    			<input type="hidden" name="car1" value="true">
  • Error Line 2563, Column 56: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="hidden" name="roundtrip" value="false">

    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 2563, Column 4: start tag was here
    			<input type="hidden" name="roundtrip" value="false">
  • Error Line 2581, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 2585, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
    								"jqtranformdone jqTransformInput" style="width: 80px;">

    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 2584, Column 9: start tag was here
    								<input type="text" id="from5" name="date1" value="" size="8" class=
  • Error Line 2595, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 2599, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
    								"jqtranformdone jqTransformInput" style="width: 80px;">

    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 2598, Column 9: start tag was here
    								<input type="text" id="to5" name="date2" value="" size="8" class=
  • Error Line 2634, Column 20: ID "carro1" already defined
    	     	<select id="carro1" name="car_type" class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1737, Column 20: ID "carro1" first defined here
    	     	<select id="carro1" name="car_type" class="jqTransformHidden">
  • Error Line 2692, Column 19: ID "chegada" already defined
    		    <select id="chegada" name='time1' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1345, Column 19: ID "chegada" first defined here
    		   	<select id="chegada" name='time1' class="jqTransformHidden">
  • Error Line 2762, Column 19: ID "chegada" already defined
    		    <select id="chegada" name='time2' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1345, Column 19: ID "chegada" first defined here
    		   	<select id="chegada" name='time1' class="jqTransformHidden">
  • Error Line 2823, Column 55: end tag for "input" omitted, but OMITTAG NO was specified
    	    	<input type="hidden" name="search" value="true">

    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 2823, Column 7: start tag was here
    	    	<input type="hidden" name="search" value="true">
  • Error Line 2824, Column 55: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="hidden" name="activity1" value="true">

    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 2824, Column 4: start tag was here
    			<input type="hidden" name="activity1" value="true">
  • Error Line 2826, Column 55: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="hidden" name="roundtrip" value="true">

    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 2826, Column 4: start tag was here
    			<input type="hidden" name="roundtrip" value="true">
  • Error Line 2843, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 2847, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
    								"jqtranformdone jqTransformInput" style="width: 80px;">

    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 2846, Column 9: start tag was here
    								<input type="text" id="from6" name="date1" value="" size="8" class=
  • Error Line 2857, Column 66: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<div class="jq-transform-input-wrapper" style="width: 90px;">

    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 "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 2861, Column 77: end tag for "input" omitted, but OMITTAG NO was specified
    								"jqtranformdone jqTransformInput" style="width: 80px;" name="date2">

    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 2860, Column 9: start tag was here
    								<input type="text" id="to6" value="" size="8" class=
  • Error Line 2887, Column 19: ID "chegada" already defined
    		   	<select id="chegada" name='time1' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1345, Column 19: ID "chegada" first defined here
    		   	<select id="chegada" name='time1' class="jqTransformHidden">
  • Error Line 2914, Column 19: ID "chegada" already defined
    		   	<select id="chegada" name='time2' class="jqTransformHidden">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1345, Column 19: ID "chegada" first defined here
    		   	<select id="chegada" name='time1' class="jqTransformHidden">
  • Error Line 2974, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
    									"jqtranformdone jqTransformInput" style="width: 160px;">

    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 2973, Column 10: start tag was here
    									<input type="text" name="pnr" id="Codigodereserva1" size="16" class=
  • Error Line 2986, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
    									"jqtranformdone jqTransformInput" style="width: 160px;">

    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 2985, Column 10: start tag was here
    									<input type="text" id="email-contato" name="email" size="16" class=
  • Error Line 3002, Column 83: ID "form1" already defined
    …action="http://viajemais.voeazul.com.br/Search2.aspx" method="post" id="form1">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 2960, Column 83: ID "form1" first defined here
    …action="http://viajemais.voeazul.com.br/Search2.aspx" method="post" id="form1">
  • Error Line 3015, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
    									"jqtranformdone jqTransformInput" style="width: 160px;">

    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 3014, Column 10: start tag was here
    									<input type="text" id="Nomedeusuario1" name="login" size="16" class=
  • Error Line 3027, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
    									"jqtranformdone jqTransformInput" style="width: 160px;">

    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 3026, Column 10: start tag was here
    									<input type="password" id="Senha2" name="password" size="16" class=
  • Error Line 3030, Column 79: ID "modal" already defined
    …href="#esquiciemail;462;370;" class="esqueci" name="modal" id="modal">Esqueci o

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 2990, Column 73: ID "modal" first defined here
    …href="#esquiciemail;462;370;" class="esqueci" name="modal" id="modal">Esqueci o
  • Error Line 3069, Column 99: ID "form1" already defined
    …pps.voeazul.com.br/AzulWebCheckin/Access/ListBooking" method="post" id="form1">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 2960, Column 83: ID "form1" first defined here
    …action="http://viajemais.voeazul.com.br/Search2.aspx" method="post" id="form1">
  • Error Line 3094, Column 112: end tag for "input" omitted, but OMITTAG NO was specified
    …CPFNumber" name="value" class="jqtranformdone jqTransformInput" maxlength="11">

    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 3094, Column 9: start tag was here
    								<input type="text"  id="CPFNumber" name="value" class="jqtranformdone j…
  • Error Line 3109, Column 99: ID "form1" already defined
    …pps.voeazul.com.br/AzulWebCheckin/Access/ListBooking" method="post" id="form1">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 2960, Column 83: ID "form1" first defined here
    …action="http://viajemais.voeazul.com.br/Search2.aspx" method="post" id="form1">
  • Error Line 3120, Column 94: end tag for "input" omitted, but OMITTAG NO was specified
    … type="text" id="Codigo1" name="value" class="jqtranformdone jqTransformInput">

    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 3120, Column 9: start tag was here
    								<input type="text" id="Codigo1" name="value" class="jqtranformdone jqTr…
  • Error Line 3135, Column 99: ID "form1" already defined
    …pps.voeazul.com.br/AzulWebCheckin/Access/ListBooking" method="post" id="form1">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 2960, Column 83: ID "form1" first defined here
    …action="http://viajemais.voeazul.com.br/Search2.aspx" method="post" id="form1">
  • Error Line 3147, Column 101: end tag for "input" omitted, but OMITTAG NO was specified
    …text" id="Numerotudoazul" name="value" class="jqtranformdone jqTransformInput">

    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 3147, Column 9: start tag was here
    								<input type="text" id="Numerotudoazul" name="value" class="jqtranformdo…
  • Error Line 3180, Column 80: ID "form1" already defined
    …action="http://viajemais.voeazul.com.br/Search2.aspx" method="post" id="form1">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 2960, Column 83: ID "form1" first defined here
    …action="http://viajemais.voeazul.com.br/Search2.aspx" method="post" id="form1">
  • Error Line 3209, Column 217: end tag for "input" omitted, but OMITTAG NO was specified
    …"firstName" class="jqtranformdone jqTransformInput" style=""></div></div></div>

    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 3209, Column 116: start tag was here
    …class="jq-transform-input-inner"><div><input type="text" id="Nome1" name="firs…
  • Error Line 3213, Column 221: end tag for "input" omitted, but OMITTAG NO was specified
    …="lastName" class="jqtranformdone jqTransformInput" style=""></div></div></div>

    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 3213, Column 116: start tag was here
    …class="jq-transform-input-inner"><div><input type="text" id="Sobrenome1" name=…
  • Error Line 3232, Column 325: ID "IndoPara9" already defined
    …'txtBusca18','divCombo18',destino)}; this._haschanged=false;" id="IndoPara9" />

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 2833, Column 277: ID "IndoPara9" first defined here
    …(!this._haschanged){this.value='';}; this._haschanged=false;" id="IndoPara9" />
  • Error Line 3242, Column 238: end tag for "input" omitted, but OMITTAG NO was specified
    …s="somenteidaData jqtranformdone jqTransformInput" style=""> </div></div></div>

    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 3242, Column 122: start tag was here
    …class="jq-transform-input-inner"><div><input type="text" id="somenteidaData6" …
  • Error Line 3360, Column 16: ID "content-dialog-middle" already defined
          <div id="content-dialog-middle" class="content-dialog"> <a href="#" class…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 3343, Column 16: ID "content-dialog-middle" first defined here
          <div id="content-dialog-middle" class="content-dialog"> <a href="#" class…
  • Error Line 3424, Column 10: ID "boxes" already defined
    <div id="boxes"><div id="esquicisenha" class="window">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 3169, Column 10: ID "boxes" first defined here
    <div id="boxes" class="boxes_home">
  • Error Line 3445, Column 91: ID "form1" already defined
    …action="http://viajemais.voeazul.com.br/Search2.aspx" method="post" id="form1">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 2960, Column 83: ID "form1" first defined here
    …action="http://viajemais.voeazul.com.br/Search2.aspx" method="post" id="form1">
  • Error Line 3477, Column 16: ID "mensagemerrobox" already defined
    </div><div id="mensagemerrobox" class="window">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 3306, Column 16: ID "mensagemerrobox" first defined here
          <div id="mensagemerrobox" class="window">
  • Error Line 3496, Column 25: ID "mensagemerro" already defined
                   		<p id="mensagemerro"></p>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 3323, Column 32: ID "mensagemerro" first defined here
                          		<p id="mensagemerro"></p>
  • Error Line 3513, Column 63: ID "errobox" already defined
    …lay:none;"><a href="#mensagemerrobox;565;;" id="errobox" name="modal" ></a></p>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 3414, Column 66: ID "errobox" first defined here
    …:none;"><a href="#mensagemerrobox;565;220;" id="errobox" name="modal" ></a></p>
  • Error Line 3525, Column 113: syntax of attribute value does not conform to declared value
    …aspx' title='Minhas reservas' target=''>Minhas reservas</a></li><li><a href='h…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3525, Column 237: syntax of attribute value does not conform to declared value
    …spx' title='Check-in On-line' target=''>Check-in On-line</a></li><li><a href='…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3525, Column 364: syntax of attribute value does not conform to declared value
    …n.aspx' title='Status de Voo' target=''>Status de Voo</a></li><li><a href='/se…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3525, Column 437: syntax of attribute value does not conform to declared value
    …='/servicos' title='Serviços' target=''>Serviços</a></li><li><a href='/informa…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3525, Column 523: syntax of attribute value does not conform to declared value
    …a-viajar' title='Informações' target=''>Informações</a></li><li><a href='/novo…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3525, Column 603: syntax of attribute value does not conform to declared value
    …a-azul' title='Novo na Azul?' target=''>Novo na Azul?</a></li><li><a href='/pa…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3525, Column 698: syntax of attribute value does not conform to declared value
    …omocionais' title='Promoções' target=''>Promoções</a></li><li><a href='http://…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3525, Column 796: syntax of attribute value does not conform to declared value
    …www.voetrip.com.br/fretamento' title='Fretamento' target=''>Fretamento</a></li>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3533, Column 81: syntax of attribute value does not conform to declared value
    …l/onibus-azul' title='Ônibus' target=''>Ônibus</a></li><li><a href='/experienc…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3533, Column 206: syntax of attribute value does not conform to declared value
    …' title='Estacionamento Azul' target=''>Estacionamento Azul</a></li><li><a hre…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3533, Column 309: syntax of attribute value does not conform to declared value
    …s-da-azul' title='Lojas Azul' target=''>Lojas Azul</a></li><li><a href='/exper…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3533, Column 402: syntax of attribute value does not conform to declared value
    …aco-azul' title='Espaço Azul' target=''>Espaço Azul</a></li><li><a href='/expe…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3533, Column 505: syntax of attribute value does not conform to declared value
    …a-azul' title='Assento extra' target=''>Assento extra</a></li><li><a href='/ex…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3533, Column 599: syntax of attribute value does not conform to declared value
    …v-ao-vivo' title='TV ao Vivo' target=''>TV ao Vivo</a></li><li><a href='/exper…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 3533, Column 680: character "&" is the first character of a delimiter but occurred as data
    …cia-azul/lanches-azul' title='Bebidas & Snacks' target=''>Bebidas & Snacks</a>…

    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 3533, Column 698: syntax of attribute value does not conform to declared value
    …zul' title='Bebidas & Snacks' target=''>Bebidas & Snacks</a></li><li><a href='…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 3533, Column 708: character "&" is the first character of a delimiter but occurred as data
    …='Bebidas & Snacks' target=''>Bebidas & Snacks</a></li><li><a href='/experienc…

    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 3533, Column 809: syntax of attribute value does not conform to declared value
    …ra' title='Reserva em espera' target=''>Reserva em espera</a></li><li><a href=…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3533, Column 935: syntax of attribute value does not conform to declared value
    …a-viagem-azul' title='Assistência Viagem' target=''>Assistência Viagem</a></li>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3541, Column 69: syntax of attribute value does not conform to declared value
    …re-azul' title='Sobre a Azul' target=''>Sobre a Azul</a></li><li><a href='/map…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3541, Column 148: syntax of attribute value does not conform to declared value
    …-rotas' title='Mapa de Rotas' target=''>Mapa de Rotas</a></li><li><a href='htt…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3541, Column 634: syntax of attribute value does not conform to declared value
    …asp' title='Trabalhe na Azul' target=''>Trabalhe na Azul</a></li><li><a href='…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3541, Column 740: syntax of attribute value does not conform to declared value
    …tle='Política de Privacidade' target=''>Política de Privacidade</a></li><li><a…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3541, Column 847: syntax of attribute value does not conform to declared value
    … title='Perguntas Frequentes' target=''>Perguntas Frequentes</a></li><li><a hr…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3541, Column 934: syntax of attribute value does not conform to declared value
    … title='Academia de Serviços' target=''>Academia de Serviços</a></li><li><a hr…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3541, Column 1020: syntax of attribute value does not conform to declared value
    …i><li><a href='/azul-e-trip' title='Azul e Trip' target=''>Azul e Trip</a></li>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3549, Column 96: syntax of attribute value does not conform to declared value
    …/' title='Conheça o Programa' target=''>Conheça o Programa</a></li><li><a href…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3549, Column 213: syntax of attribute value does not conform to declared value
    …zul/tiers' title='Categorias' target=''>Categorias</a></li><li><a href='https:…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3549, Column 326: syntax of attribute value does not conform to declared value
    …Register' title='Cadastre-se' target=''>Cadastre-se</a></li><li><a href='https…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3549, Column 461: syntax of attribute value does not conform to declared value
    … title='Perguntas frequentes' target=''>Perguntas frequentes</a></li><li><a hr…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3549, Column 596: syntax of attribute value does not conform to declared value
    …b/azul/terms-and-conditions' title='Regulamento' target=''>Regulamento</a></li>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 3602, Column 329: end tag for element "br" which is not open
    …do Azul não tem limitação de assentos e independe de baixa e alta estação.</br>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 3641, Column 18: character "&" is the first character of a delimiter but occurred as data
    			if(popup_chat && !popup_chat.closed){

    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 3641, Column 19: character "&" is the first character of a delimiter but occurred as data
    			if(popup_chat && !popup_chat.closed){

    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 3687, Column 102: cannot generate system identifier for general entity "cdp"
    …http://aunica.112.2o7.net/b/ss/unica-azul-dev/1/H.23.3--NS/0?[AQB]&cdp=3&[AQE]"

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 3687, Column 102: general entity "cdp" not defined and no default entity
    …http://aunica.112.2o7.net/b/ss/unica-azul-dev/1/H.23.3--NS/0?[AQB]&cdp=3&[AQE]"

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 3687, Column 105: reference not terminated by REFC delimiter
    …http://aunica.112.2o7.net/b/ss/unica-azul-dev/1/H.23.3--NS/0?[AQB]&cdp=3&[AQE]"

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 3687, Column 105: reference to external entity in attribute value
    …http://aunica.112.2o7.net/b/ss/unica-azul-dev/1/H.23.3--NS/0?[AQB]&cdp=3&[AQE]"

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 3687, Column 105: reference to entity "cdp" for which no system identifier could be generated
    …http://aunica.112.2o7.net/b/ss/unica-azul-dev/1/H.23.3--NS/0?[AQB]&cdp=3&[AQE]"

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 3687, Column 101: entity was defined here
    …http://aunica.112.2o7.net/b/ss/unica-azul-dev/1/H.23.3--NS/0?[AQB]&cdp=3&[AQE]"
  • Warning Line 3687, Column 107: character "&" is the first character of a delimiter but occurred as data
    …http://aunica.112.2o7.net/b/ss/unica-azul-dev/1/H.23.3--NS/0?[AQB]&cdp=3&[AQE]"

    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 1478, Column 16: reference to non-existent ID "idade1"
    		 <label for="idade1">Selecione a idade de cada crian&ccedil;a.</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 1482, Column 15: reference to non-existent ID "idade1"
     	<label for="idade1"> Crian&ccedil;a 1</label> 

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 1540, Column 14: reference to non-existent ID "idade1"
    	<label for="idade1"> Crian&ccedil;a 2</label> 

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 1595, Column 13: reference to non-existent ID "idade1"
    <label for="idade1"> Crian&ccedil;a 3</label> 

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 1992, Column 16: reference to non-existent ID "idade1"
    		 <label for="idade1">Selecione a idade de cada crian&ccedil;a.</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 1996, Column 15: reference to non-existent ID "idade1"
     	<label for="idade1"> Crian&ccedil;a 1</label> 

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 2054, Column 14: reference to non-existent ID "idade1"
    	<label for="idade1"> Crian&ccedil;a 2</label> 

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 2109, Column 13: reference to non-existent ID "idade1"
    <label for="idade1"> Crian&ccedil;a 3</label> 

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 2375, Column 16: reference to non-existent ID "idade1"
    		 <label for="idade1">Selecione a idade de cada crian&ccedil;a.</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 2379, Column 15: reference to non-existent ID "idade1"
     	<label for="idade1"> Crian&ccedil;a 1</label> 

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 2437, Column 14: reference to non-existent ID "idade1"
    	<label for="idade1"> Crian&ccedil;a 2</label> 

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 2492, Column 13: reference to non-existent ID "idade1"
    <label for="idade1"> Crian&ccedil;a 3</label> 

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 21.000 visits

In Page Analysis