w3c-validation | 易学教程

Validation error: Byte-Order Mark found in UTF-8 File

阅读更多关于 Validation error: Byte-Order Mark found in UTF-8 File

问题 I'm working on a website and while displaying it on Firefox is fine, on IE I've got a lot of problems. I used the w3c validator and I got a lot of strange errors. Here's the link to the website: http://misenplacecatering.it/ The first validation error, I think the most relevant, is this: Byte-Order Mark found in UTF-8 File. The Unicode Byte-Order Mark (BOM) in UTF-8 encoded files is known to cause problems for some text editors and older browsers. You may want to consider avoiding its use

HTML validation error: Non-space characters found before DOCTYPE

阅读更多关于 HTML validation error: Non-space characters found before DOCTYPE

问题 I have a blog(wordpress based). And try to validate by w3c validator one of my page. The first error is: Line 1, Column 1: Non-space characters found without seeing a doctype first. Expected <!DOCTYPE html>. <!DOCTYPE html> Also, DebugBar (http://www.my-debugbar.com/wiki/IETester/HomePage) agree and show two invisible chars before <! when I open the same page from "HTML Check" tab inside this tool. BUT!! This line of HTML-code come from file header.php in my wordpress theme. I

There is no attribute “allowtransparency”

阅读更多关于 There is no attribute “allowtransparency”

问题 I am looking for some alternate way to do: <iframe transparency=true ... When I do the W3C validation, I am getting the error: Column 31: there is no attribute "allowtransparency" If use this CSS, .iframe-trans-fix{ opacity: 0; filter:alpha(opacity=0); } for the above snippet I am getting a blank iframe. 回答1: While it's true that the W3C's HTML spec does not define it, there is an allowTransparency attribute, and it is supported by all modern browsers (and Internet Explorer). As HTML5 has

There is no attribute “allowtransparency”

阅读更多关于 There is no attribute “allowtransparency”

Parse errors when using calc with rem and px

阅读更多关于 Parse errors when using calc with rem and px

问题 I have the following CSS: body { width: calc(700px + 2 * 4rem); } .someclass { margin: calc(2rem - 2px) 0; } When I run this through the W3C CSS validation, I get Value Error : width Parse Error + 2 * 4rem) Value Error : margin Parse Error - 2px) 0 What’s causing this? All the units I’m using in calc() are length units, and calc() should be able to handle it. 回答1: This is a known bug in w3 css validator: https://www.w3.org/Bugs/Public/show_bug.cgi?id=18913 来源： https://stackoverflow.com

“Attribute name not allowed on element div at this point”

阅读更多关于 “Attribute name not allowed on element div at this point”

问题 I am getting a W3V validator error that I can't understand: Line 31, Column 61: Attribute name not allowed on element div at this point. That is this row: <div name="message" class="jGrowl bottom-right errorGrowl"></div> Full HTML: <!DOCTYPE html> <html> <head> <title>jGrowl</title> <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"> <script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/1.5.0/jquery.min.js"></script> <script type="text/javascript" src

HTML5 valid namespace tag prefixes

阅读更多关于 HTML5 valid namespace tag prefixes

问题 When validating my page, the W3-Validator gives me an error for every <tag addthis:title="AddThis share title" /> attribute in my code. How can I make those attributes valid for HTML5, so the page validates? I need those tags so addthis uses the correct titles for my sharing links, so I can't get rid of them... 回答1: You can't make them valid. Not in HTML, not in XHTML. The only valid custom attributes allowed in HTML5 start "data-". You could make your markup valid HTML5+something or XHTML5

AngularJS directives as “custom” HTML tags: isn't this dangerous and may conflict with future HTML versions?

阅读更多关于 AngularJS directives as “custom” HTML tags: isn't this dangerous and may conflict with future HTML versions?

问题 I'm currently reading a lot about different JS frameworks (EmberJS, AngularJS, etc.). On first sight, I loved AngularJS' idea of using directives like custom HTML tags: <mytag>...</mytag> But isn't this dangerous? If I define a lot of such tags, then there's a high likelihood that a future HTML spec may also define one of my custom tags, but with a whole other meaning! I know that custom tags may be allowed by the HTML spec itself: http://w3c.github.io/webcomponents/spec/custom/ But at the

What practice to use for HTML5 scoped attribute

阅读更多关于 What practice to use for HTML5 scoped attribute

问题 I went to validate my HTML5 page today using the w3c validator and recieved an error message saying the style tag must have the scoped attribute if its not in the head section. So I added the scope attribute to my style tag and now I am getting this warning from the validator, The scoped attribute on the style element is not supported by browsers yet. It would probably be better to wait for implementations. So which is it? Use the scoped attribute, or dont? If I do not then I am getting an

Google +1 code validation error: missing attribute

阅读更多关于 Google +1 code validation error: missing attribute

问题 My code: <g:plusone annotation="inline"></g:plusone> I get this error: there is no attribute "annotation" element "g:plusone" undefined Why? 回答1: You have two choices Change to using this style markup <div class="g-plusone" data-size="tall" ... ></div> Add the XML NS for google's <g: syntax to the <html tag of the document. Now if only Google would share where that xml namespace is located... (So really, just try option 1) 回答2: There is no attribute called "annotation" for any element