Julian P | 1 Jul 01:21 2015

Google Searchbox Not Validating as HTML5

Hi!  I have added the Google searchbox to my HTML5 site. When I go to the
W3C validator I get an error: 'element gcse:search not allowed as child of
element div in this context'. I was instructed by Google to put the script
in a div, and cannot get the searchbox to work without it. My code is below.
Many thanks!  Julian

<div id="searchbox">    
       (function() {    
            var cx = '014531685129972083622:vk5kxnojpx0';    
            var gcse = document.createElement('script');    
            gcse.type = 'text/javascript';    
            gcse.async = true;    
            gcse.src = (document.location.protocol == 'https:' ? 'https:' :
'http:') + '//www.google.com/cse/cse.js?cx=' + cx;

            var s = document.getElementsByTagName('script')[0];

            s.parentNode.insertBefore(gcse, s);


    <gcse:search> </gcse:search>    

Jon Freeland | 30 Jun 21:06 2015

Nu HTML checker issue

Dear sirs,

I am hoping that there will be a future option to remove having the 
skeleton html when doing text uploads. Really annoying to have to clear it 
out every time. Should be an empty box so that it can be copied/pasted 
easier when testing script generated source.

Thanks! =)




Vladislav Bushurov | 29 Jun 17:59 2015

validation error message


Line 48, Column 155Bad value handheld, screen and (max-width: 640px), only screen and (max-device-width: 640px) for attribute media on element link: Expected a CSS media type but the query ended.

Line 49, Column 199Bad value screen and (min-width: 641px) and (max-width: 959px), only screen and (min-device-width: 641px) and (max-device-width: 959px) for attribute media on element link: Expected a CSS media feature but saw min-device-width instead.

Two days ago there was no one error in this place.
Are there errors in the code indeed?
New rules?
What's happened?


Is that not valid?

Vladislav Bushurov
Alexandr Real Estate
Admiralteysky Division
5 ul.Dekabristov, St.Petersburg
Russia, 190000
Franz J Fortuny L | 29 Jun 19:17 2015

Error reporting an error which is NOT

I have this line in my HTML5 page:

The error reporting tool is giving me these errors:

  1. Error: & did not start a character reference. (& probably should have been escaped as &amp;.)

    At line 20, column 91


  2. Error: & did not start a character reference. (& probably should have been escaped as &amp;.)

    At line 20, column 114


Tara Gibson | 23 Jun 10:41 2015

Error in site

I have website Phone Detective which is showing 22 errors but my programmer has left the job so its very difficult for me to edit it, is there any option to solve this problem.

i am also seeing errors in my other site too

Whatsapp Status
Whatsapp Spy Android



Kathy Goss | 19 Jun 15:33 2015

Problem with feed validation when using SSL SNI


One of my domains is not able to create a Mailchimp RSS campaign. I get the message that the URL is not a valid RSS feed. Although you can access the URL without errors,  the WC3 RSS Validation Service that Mailchimp uses gets the following error:

Server returned [Errno 1] _ssl.c:504: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error

During a chat with my hosting provider this morning I was told that since it is an SSL related issue to check at Cloudflare.

Cloudflare's response was:  "The Validator service not supporting SNI is a known issue; unfortunately there is little we can do about this; the validator service needs to be updated to support this."

The domain is:  shelbysessentials.com

Do you intend to update your service to support SNI and if so when or at least is there a way to exclude this error in your validation.  We have hundreds of sites and we include Mailchimp integration and part of our service is to set our subscribers up with RSS driven campaigns but this issue is blocking our ability.  Please advise.

Kathy Goss

Using Essential Oils, LLC



NOTE: Whenever possible, give the address of the document you were checking.

Alberto Nannini | 19 Jun 00:43 2015

IO error

your validator rise up an "IO error" validating my site.

Here is my homepage url: http://www.notanumber.it/en/

Let me know if there is something wrong.

IMHO there are some problems in the validator.

Thanks in advance,

Tel. +39.333.98.68.401

Proprietà Intellettuale della Webrevolver.
Le informazioni contenute in questo documento sono destinate esclusivamente all'uso personale e riservato del destinatario e pertanto ne è vietato qualsiasi utilizzo da parte di terzi. I Clienti destinatari sono soggetti alle condizioni stabilite nel contratto stipulato ed alle vigenti normative in tutela della Privacy. Ogni riferimento non attinente alle attività di Webrevolver è da intendere come "non approvato". Qualsivoglia utilizzo non autorizzato del documento costituisce violazione.
Eckhard Schönknecht | 12 Jun 13:01 2015

.info Domains are real Internet Adresses, believe me, were in 2015


Hello from germany

today i want to check 2 Adresses from me 4 fun and:


cannot be checked. Message in Germany: "Bitte geben Sie eine Internet
Adresse ein".


Please check your "formula-checkings" (sorry for my bad English)



Attachment (smime.p7s): application/pkcs7-signature, 5081 bytes
Mellem, Dan | 13 Jun 02:53 2015

[VE][64] Confusing error when title missing

When validating:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<p> test

You get the error:
Error [64]: "document type does not allow element X here"

However, it would be clearer to report that the <title></title> section is missing or show [VE][73], but
this is only shows if there's a "</head>."

Adding a title validates:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<p> test


KENNETH LUNN | 10 Jun 19:50 2015

Nu Html Checker suggestions



I would like to suggest some improvements to the "Nu Html Checker", if they're not too problematical to implement.

  1. In the 'Checker Input' box, remember the value of the Show (Source/Outline/Image report) from file to file and from session to session.
  2. In the 'Checker Input' box, remember the 'Check by' value (address/file input/text input).
  3. In the 'Checker Input' box, remember the 'Choose file' name; clicking on it opens the last used directory name, so it looks as though you're almost there!
  4. When an 'Error' is found, a link straight to the offending item would be great. Possibly the same goes for an associated 'Warning' as that might be the real error.

Regards and thanks for providing such a useful tool.

Ken Lunn

Kelvin Warne | 8 Jun 16:21 2015

HTML validator - A safeguard for old browsers is flagged up as an error

Hello w3 org,
Thank you for your very useful validators; I use them regularly.
When I insert an anchor in a page, I follow the advice in the w3 reference material and use eg. <a id="TopofPage" name="TopofPage"></a> to cater for old (name) as well as current (id) browsers. This is flagged as an error in your validators (both the original and your Nu Html checker).
NB. A similar situation arises in the css checker when using the older IE Opacity style statement as well as the current one.
I hope this is helpful.
Thank you and Kind Regards
kelvin <at> kwservices.co.uk