w3c-validation | 易学教程

W3C validator: “handshake alert: unrecognized_name”

阅读更多关于 W3C validator: “handshake alert: unrecognized_name”

问题 I am trying to validate my website on W3C Nu Html Checker but I am getting below error, don't know why? IO Error: handshake alert: unrecognized_name While my website is working fine on SSL. I tried Handshake alert: unrecognized_name error , but no help. any guidance how to fix this much helpful. I didn't have that much knowledge of server. 来源： https://stackoverflow.com/questions/33580702/w3c-validator-handshake-alert-unrecognized-name

Why does http-equiv=“X-UA-Compatible” content=“IE=edge,chrome=1” is not validated in W3C Validator? [duplicate]

阅读更多关于 Why does http-equiv=“X-UA-Compatible” content=“IE=edge,chrome=1” is not validated in W3C Validator? [duplicate]

问题 This question already has answers here : Bad value X-UA-Compatible for attribute http-equiv on element meta (8 answers) Closed 4 years ago . I have: <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" /> On validation in http://validator.w3.org/ I get this error: A meta element with an http-equiv attribute whose value is X-UA-Compatible must have a content attribute with the value IE=edge. I am working with .NET/Razor and of course locally using IIS . Is there a way to solve this

Why do internal TABLE sections have to go THEAD TFOOT TBODY to validate?

阅读更多关于 Why do internal TABLE sections have to go THEAD TFOOT TBODY to validate?

问题 I often use THEAD, TBODY, and TFOOT elements to divide my data tables into sections that can be addressed separately with CSS. I also understand that there is always an implicit TBODY tag. What puzzles me is the order that these have to go in to validate. THIS table will validate: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en"> <head> <meta http-equiv="Content-Type"

Ampersands in hyperlinks cause W3C validation to fail

阅读更多关于 Ampersands in hyperlinks cause W3C validation to fail

问题 I have a reacurring problem. I code nice standards compliant code only to have it fail due to ampersands within some of the hyperlink urls. Does anyone know of a work around or hack for this. Thanks 回答1: You should URL Encode the hyperlinks, so all characters are turned into a valid ASCII format and don't contain any (X)HTML entities. For C# use HttpUtility.UrlEncode, for PHP urlencode, for JavaScript encodeURI , etc... Finding the right method for the language you're using shouldn't be that

Ampersands in hyperlinks cause W3C validation to fail

阅读更多关于 Ampersands in hyperlinks cause W3C validation to fail

Element style not allowed as child of element body in this context (<style scoped> not validating)

阅读更多关于 Element style not allowed as child of element body in this context ( not validating)

问题 <!DOCTYPE html> ... <style scoped> /* css */ </style> The w3.org validator is giving me this error: Line 883, Column 17: Element style not allowed as child of element body in this context. (Suppressing further errors from this subtree.) <style scoped>... Contexts in which element style may be used: If the scoped attribute is absent: where metadata content is expected. If the scoped attribute is absent: in a noscript element that is a child of a head element. If the scoped attribute is present

Element name gcse:searchbox-only cannot be represented as XML 1.0

阅读更多关于 Element name gcse:searchbox-only cannot be represented as XML 1.0

问题 I am getting the following error in w3 validator, Line 62, Column 140: Element name gcse:searchbox-only cannot be represented as XML 1.0. I am using Google search bar inside website which is added by this code, <gcse:searchbox-only></gcse:searchbox-only> Please help out to avoid this error. Thanks 回答1: Michael[tm] Smith, the guy who looks after the W3C HTML validator says here: It's not an error, it's a warning. And it's emitted because the content is being served as HTML instead of with an

CSS3 calc() validation: Value Error : width Parse Error [duplicate]

阅读更多关于 CSS3 calc() validation: Value Error : width Parse Error [duplicate]

问题 This question already has an answer here : Parse errors when using calc with rem and px (1 answer) Closed 3 years ago . I need to validate a CSS3 file where I'm using the following code: width:calc(96.3% - 312px) It returns this error: Value Error : width Parse Error - 312px) My last choice is to use a Javascript function on page load and window resize to get the width value when it's possible using CSS3 (only for IE8 or older). 回答1: This appears to be a bug in the validator. Your calc()

“This interface to HTML5 document checking is deprecated”

阅读更多关于 “This interface to HTML5 document checking is deprecated”

问题 While doing a project I was checking it for W3C errors (using html validator plug-in for Firefox), and in the process I found a warning that never showed up to me ever before. " Warning: This interface to HTML5 document checking is deprecated" So, first thing came up to my mind, " let me Google this " and see what information I could find about this warning, but I didn't get anything. Tried another approach, which was going to the actual W3C Validator and see the outcome.But, I was given the

Does HTML5 require an action attribute for forms? [duplicate]

阅读更多关于 Does HTML5 require an action attribute for forms? [duplicate]

问题 This question already has answers here : Is action really required on forms? (4 answers) Closed 3 years ago . I've just run a webpage of mine through the W3C HTML5 validator, and it validates completely, even though the form in it doesn't have an action attribute, which the HTML 4 validator always complains about. Considering the fact that the HTML5 validator is still experimental, is the fact that the form validating despite not having an action attribute a problem with the validator, or has